Comparison Overview
NVIDIA DRIVE
NVIDIA DRIVE
Santa Clara, California, US, 95051
Last Update: 21/04/2026
From designing and visualizing vehicles, to training autonomous systems and building immersive virtual showrooms and factory digital twins, NVIDIA is redefining every stage of the automotive experience. Powered by AI, Omniverse™, and accelerated computing, we're driving...
NVIDIA
2701 San Tomas Expressway, Santa Clara, 95050, US
Last Update: 12/10/2026
Since its founding in 1993, NVIDIA (NASDAQ: NVDA) has been a pioneer in accelerated computing. The company’s invention of the GPU in 1999 sparked the growth of the PC gaming market, redefined computer graphics, ignited the era of modern AI and is fueling the creation of...
Compliance Ranges Comparison
NVIDIA DRIVE
NVIDIA
Benchmark & Cyber Underwriting Signals
Incidents vs Computer Hardware Manufacturing Industry Avg (This Year)
No incidents recorded for NVIDIA DRIVE in 2026.
Incidents vs Computer Hardware Manufacturing Industry Avg (This Year)
NVIDIA has 1370.59% more incidents than the average of all companies with at least one recorded incident.
Incident History - NVIDIA DRIVE (X = Date, Y = Severity)
NVIDIA DRIVE cyber incidents detection timeline including parent company and subsidiaries.
Incident History - NVIDIA (X = Date, Y = Severity)
NVIDIA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
NVIDIA DRIVE
NVIDIA
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.