Comparison Overview
Škoda Auto

Škoda Auto
Václava Klementa 869, Mladá Boleslav, 293 60, CZ
Last Update: 12/05/2026
Since 1895, we have been creating progressive contemporary vehicles. This approach was first applied to bicycles, followed by motorcycles and finally cars. For more than 125 years, we have combined design, the latest technology, functionality and innovation in everythin...

PACCAR
777 106th Ave NE, Bellevue, 98004, US
Last Update: 30/03/2026
PACCAR is a global technology leader in the design, manufacture and customer support of premium light-, medium- and heavy-duty trucks under the Kenworth, Peterbilt and DAF nameplates. PACCAR also designs and manufactures advanced diesel engines, provides financial servi...
Compliance Ranges Comparison

Škoda Auto







PACCAR






Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
Škoda Auto has 57.45% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for PACCAR in 2026.
Incident History - Škoda Auto (X = Date, Y = Severity)
Škoda Auto cyber incidents detection timeline including parent company and subsidiaries.
Incident History - PACCAR (X = Date, Y = Severity)
PACCAR cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Škoda Auto

PACCAR
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.