Comparison Overview
Metso

Metso
Rauhalanpuisto 9, Espoo, 02230, FI
Last Update: 03/04/2026
Metso is a frontrunner in sustainable technologies, end-to-end solutions and services for the aggregates, minerals processing and metals refining industries globally. By improving our customers’ energy and water efficiency, increasing their productivity, and reducing ...

Mitsubishi Heavy Industries
2−3 Marunouchi 3-Chome, Chiyoda-ku, 100-8332, JP
Last Update: 13/09/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 ...
Compliance Ranges Comparison

Metso







Mitsubishi Heavy Industries






Benchmark & Cyber Underwriting Signals
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Metso in 2026.
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Mitsubishi Heavy Industries in 2026.
Incident History - Metso (X = Date, Y = Severity)
Metso cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mitsubishi Heavy Industries (X = Date, Y = Severity)
Mitsubishi Heavy Industries cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Metso

Mitsubishi Heavy Industries
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout