Comparison Overview
Thales Transport

Thales Transport
60 Ludgate Hill, London, EC4M 7AW, GB
Last Update: 04/04/2026
Following the acquisition of Thales Transport by Hitachi Rail, this account is no longer active. Please follow Hitachi Rail for all future updates from our team.

Amtrak
1 Massachusetts Ave NW, Washington, 20002, US
Last Update: 27/07/2026
Moving America Where it wants to go. We are not just a railroad; we are a company that moves people. With 21,000 route miles in 46 states, the District of Columbia and three Canadian provinces, Amtrak operates more than 300 trains each day – at speeds up to 150 mph – t...
Compliance Ranges Comparison

Thales Transport







Amtrak






Benchmark & Cyber Underwriting Signals
Incidents vs Rail Transportation Industry Avg (This Year)
No incidents recorded for Thales Transport in 2026.
Incidents vs Rail Transportation Industry Avg (This Year)
Amtrak has 94.17% more incidents than the average of all companies with at least one recorded incident.
Incident History - Thales Transport (X = Date, Y = Severity)
Thales Transport cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Amtrak (X = Date, Y = Severity)
Amtrak cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Thales Transport

Amtrak
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.