Comparison Overview
Great Western Railway (GWR)
Great Western Railway (GWR)
Milford House, Swindon, SN1 1HL, GB
Last Update: 09/03/2026
As one of the largest train companies in Britain, more than 100 million customers a year join us on board. When the Great Western Railway was built, it opened the West and Wales to trade and tourism. And now, along with our partners at Network Rail, we’re proud to have ...
Hitachi Rail
60 Ludgate Hill, 7th Floor, One New Ludgate, London, England, GB, EC4M 7AW
Last Update: 02/04/2026
Hitachi Rail is committed to driving a sustainable mobility transition and helping every passenger, customer and community enjoy more connected, seamless and sustainable transport. Hitachi Rail is a trusted partner to operators around the world with expertise across eve...
Compliance Ranges Comparison
Great Western Railway (GWR)
Hitachi Rail
Benchmark & Cyber Underwriting Signals
Incidents vs Rail Transportation Industry Avg (This Year)
No incidents recorded for Great Western Railway (GWR) in 2026.
Incidents vs Rail Transportation Industry Avg (This Year)
No incidents recorded for Hitachi Rail in 2026.
Incident History - Great Western Railway (GWR) (X = Date, Y = Severity)
Great Western Railway (GWR) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hitachi Rail (X = Date, Y = Severity)
Hitachi Rail cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Great Western Railway (GWR)
Hitachi 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: *.*.