Comparison Overview
Thermax Sub-Saharan Africa
Thermax Sub-Saharan Africa
Office No.2, First Floor, Western Heights, Kenya, 353-00623, KE
Last Update: 06/12/2025
Incorporated in 1966, Thermax Group is a 1 billion USD 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 ...
Wärtsilä
Hiililaiturinkuja 2, Helsinki, 00180, FI
Last Update: 01/04/2026
We enable sustainable societies through innovation in technology and services together with all our stakeholders – today and tomorrow. We emphasise innovation in sustainable technology and services to help our customers continuously improve environmental and economic p...
Compliance Ranges Comparison
Thermax Sub-Saharan Africa
Wärtsilä
Benchmark & Cyber Underwriting Signals
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Thermax Sub-Saharan Africa in 2026.
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Wärtsilä in 2026.
Incident History - Thermax Sub-Saharan Africa (X = Date, Y = Severity)
Thermax Sub-Saharan Africa cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Wärtsilä (X = Date, Y = Severity)
Wärtsilä cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Thermax Sub-Saharan Africa
Wärtsilä
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: *.*.