Comparison Overview
Mitsubishi Logisnext Europe Oy
Mitsubishi Logisnext Europe Oy
Jampankatu 2, Järvenpää, 04400, FI
Last Update: 27/02/2026
Rocla Oy changed its name to Mitsubishi Logisnext Europe Oy. MLE Oy is a Finland-based company whose core business is to provide intelligent materials handling solutions and services. The company has grown considerably in its more than 75 years of operation and has beco...
Atlas Copco
Sickla Industriväg 19, Stockholm, SE, 131 54
Last Update: 01/04/2026
Atlas Copco delivers innovative products and solutions that help businesses grow and drive progress. Our portfolio spans compressed air and gas systems and treatment, vacuum solutions, industrial power tools, assembly systems, and power and flow solutions. We bring a ...
Compliance Ranges Comparison
Mitsubishi Logisnext Europe Oy
Atlas Copco
Benchmark & Cyber Underwriting Signals
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Mitsubishi Logisnext Europe Oy in 2026.
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Atlas Copco in 2026.
Incident History - Mitsubishi Logisnext Europe Oy (X = Date, Y = Severity)
Mitsubishi Logisnext Europe Oy cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Atlas Copco (X = Date, Y = Severity)
Atlas Copco cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Mitsubishi Logisnext Europe Oy
Atlas Copco
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: *.*.