Comparison Overview
Siemens Mobility
Siemens Mobility
Munich, DE
Last Update: 03/04/2026
Siemens Mobility, part of Siemens AG, provides rail traffic technology that helps transform the everyday for everyone. Our solutions enable customers and partners worldwide to shape the future of mobility for people, economies, and societies. We combine the real and ...
Network Rail
The Quadrant MK, Milton Keynes, MK9 1EN, GB
Last Update: 01/04/2026
We’re at the heart of revitalising Britain’s railway, getting people and goods where they need to be and supporting the economy. Investment and modernisation are essential. So we’re building the railway of the future, running a safe, reliable and efficient railway, and...
Compliance Ranges Comparison
Siemens Mobility
Network Rail
Benchmark & Cyber Underwriting Signals
Incidents vs Rail Transportation Industry Avg (This Year)
No incidents recorded for Siemens Mobility in 2026.
Incidents vs Rail Transportation Industry Avg (This Year)
No incidents recorded for Network Rail in 2026.
Incident History - Siemens Mobility (X = Date, Y = Severity)
Siemens Mobility cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Network Rail (X = Date, Y = Severity)
Network Rail cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Siemens Mobility
Network Rail
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: *.*.