Comparison Overview
Metro-North Railroad
Metro-North Railroad
undefined, New York, undefined, undefined, US
Last Update: 18/02/2026
Founded in 1983 when the MTA assumed control of Conrail commuter operations in the states of New York and Connecticut, Metro-North Railroad’s roots can be traced back to the New York & Harlem Railroad, which began in 1832 as a horse-car line in lower Manhattan. Today, w...
CSX
500 Water Street, None, Jacksonville, FL, US, 32202
Last Update: 09/04/2026
CSX is a company on the move. As the nation’s best run railroad, we’re redefining freight rail with a progressive vision and real results – setting new industry performance standards and building a force of highly skilled professionals who are energized to help us move ...
Compliance Ranges Comparison
Metro-North Railroad
CSX
Benchmark & Cyber Underwriting Signals
Incidents vs Rail Transportation Industry Avg (This Year)
No incidents recorded for Metro-North Railroad in 2026.
Incidents vs Rail Transportation Industry Avg (This Year)
No incidents recorded for CSX in 2026.
Incident History - Metro-North Railroad (X = Date, Y = Severity)
Metro-North Railroad cyber incidents detection timeline including parent company and subsidiaries.
Incident History - CSX (X = Date, Y = Severity)
CSX cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Metro-North Railroad
CSX
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: *.*.