Comparison Overview
Ford México

Ford México
Henry Ford 100, Naucalpan, Estado de México, MX, 53126
Last Update: 19/02/2026
En 2022 inauguramos el nuevo Global Technology & Business Center para dar el siguiente paso en nuestra historia y en la de nuestro país. Somos la primera marca de vehículos en tocar el suelo mexicano, y ahora, un parteaguas en el desarrollo no solo de soluciones de movi...

Volvo Group
Gropegårdsgatan 2, Göteborg, SE, 417 15
Last Update: 01/04/2026
The Volvo Group is one of the world’s leading manufacturers of trucks, buses, construction equipment and marine and industrial engines. The Group also provides complete solutions for financing and service. The Volvo Group, with its headquarters in Gothenburg, employs ab...
Compliance Ranges Comparison

Ford México







Volvo Group






Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Ford México in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
Volvo Group has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Ford México (X = Date, Y = Severity)
Ford México cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Volvo Group (X = Date, Y = Severity)
Volvo Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Ford México

Volvo Group
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.