Comparison Overview
Mitsubishi Heavy Industries
Mitsubishi Heavy Industries
2−3 Marunouchi 3-Chome, Chiyoda-ku, Tokyo, JP, 100-8332
Last Update: 01/04/2026
Mitsubishi Heavy Industries (MHI) Group is one of the world’s leading industrial firms. For more than 130 years, we have channeled big thinking into solutions that move the world forward – advancing the lives of everyone who shares our planet. We deliver innovative and ...
TK Elevator
E-Plus Straße 1, Düsseldorf, North Rhine-Westphalia, DE, 40472
Last Update: 01/04/2026
𝗪𝗲𝗹𝗰𝗼𝗺𝗲 𝘁𝗼 𝗧𝗞 𝗘𝗹𝗲𝘃𝗮𝘁𝗼𝗿 – 𝗪𝗵𝗲𝗿𝗲 𝗜𝗻𝗴𝗲𝗻𝘂𝗶𝘁𝘆 𝗘𝗹𝗲𝘃𝗮𝘁𝗲𝘀 𝗨𝗿𝗯𝗮𝗻 𝗟𝗶𝘃𝗶𝗻𝗴 Engineering pioneer. Global industry leader. TK Elevator draws on a legacy of firsts – from a groundbreaking vertical conveyor in 1890 – to evolve modern ...
Compliance Ranges Comparison
Mitsubishi Heavy Industries
TK Elevator
Benchmark & Cyber Underwriting Signals
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Mitsubishi Heavy Industries in 2026.
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for TK Elevator in 2026.
Incident History - Mitsubishi Heavy Industries (X = Date, Y = Severity)
Mitsubishi Heavy Industries cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TK Elevator (X = Date, Y = Severity)
TK Elevator cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Mitsubishi Heavy Industries
TK Elevator
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: *.*.