Comparison Overview
PACCAR México
PACCAR México
N/A
Last Update: 12/03/2026
Somos una parte del Corporativo PACCAR Inc. Company situado en Seattle, Washington en los Estados Unidos. Nuestras divisiones Kenworth Mexicana, PacLease Mexicana, PACCAR Financial y PACCAR Parts conforman el grupo PACCAR México.
Porsche AG
Porscheplatz 1, Stuttgart, D-70435, DE
Last Update: 21/09/2026
“In the beginning I looked around and could not find quite the car I dreamed of. So I decided to build it myself.“ This quote by Ferry Porsche sums up everything that makes Porsche what it is. It has been our guiding star for more than 75 years. Every day, we search fo...
Compliance Ranges Comparison
PACCAR México
Porsche AG
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for PACCAR México in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Porsche AG in 2026.
Incident History - PACCAR México (X = Date, Y = Severity)
PACCAR México cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Porsche AG (X = Date, Y = Severity)
Porsche AG cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
PACCAR México
Porsche AG
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.