Comparison Overview
Seco Tools France
Seco Tools France
22 Avenue de la Prospective, BOURGES, undefined, 18020, FR
Last Update: 05/04/2026
Seco est une entreprise internationale dont le siège est basé à Fagersta en Suède. Seco Tools est un fournisseur global de solutions complètes d’usinage pour le fraisage, le tournage, l’usinage des trous et les systèmes d’attachements. Satisfaire les exigences de nos c...
Thermax Limited
IN, IN
Last Update: 01/04/2026
Incorporated in 1966, Thermax Group is a 1 billion US$ company headquartered in Pune, India. Over the years, it has grown into a leading conglomerate in the energy and environment space and a trusted partner in energy transition. Strategically spreading its operations ...
Compliance Ranges Comparison
Seco Tools France
Thermax Limited
Benchmark & Cyber Underwriting Signals
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Seco Tools France in 2026.
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Thermax Limited in 2026.
Incident History - Seco Tools France (X = Date, Y = Severity)
Seco Tools France cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Thermax Limited (X = Date, Y = Severity)
Thermax Limited cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Seco Tools France
Thermax Limited
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.