Comparison Overview
Alfa Romeo

Alfa Romeo
Torino, IT
Last Update: 25/01/2026
For more than 110 years, Alfa Romeo has crafted and engineered some of the most legendary and exclusive cars in the history of automotive. To this day, for Alfa Romeo, technology, attention to details and an unmistakable style work together to combine beauty and purp...

Bridgestone Americas
200 4th Ave S, Nashville, US
Last Update: 03/04/2026
Bridgestone Americas, Inc. (BSAM), headquartered in Nashville, Tennessee, and Bridgestone Europe, Middle East and Africa (BSEMEA), headquartered in Brussels, Belgium, operate collectively as a “Bridgestone West” strategic region. This region services the strategic busin...
Compliance Ranges Comparison

Alfa Romeo







Bridgestone Americas






Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Alfa Romeo in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Bridgestone Americas in 2026.
Incident History - Alfa Romeo (X = Date, Y = Severity)
Alfa Romeo cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bridgestone Americas (X = Date, Y = Severity)
Bridgestone Americas cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Alfa Romeo

Bridgestone Americas
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.