Comparison Overview
Audi Stuttgart GmbH

Audi Stuttgart GmbH
Heilbronner Straße 340, Stuttgart, 70469, DE
Last Update: 25/02/2026
Herzlichen willkommen bei Audi Stuttgart GmbH – Ihrem Partner für Vorsprung durch Technik in der Region! Mit unseren Standorten in Feuerbach, Vaihingen und Böblingen bieten wir mit unseren knapp 400 Mitarbeiterinnen und Mitarbeitern ein umfassendes Angebot rund um die M...

BorgWarner
3850 Hamlin Rd, Auburn Hills, Michigan, US, 48326
Last Update: 01/04/2026
As a global product leader for over 130 years, we deliver innovative and sustainable mobility solutions. Guided by our commitment to inclusion, integrity, excellence, responsibility and collaboration—and our pledge to reach carbon neutrality by 2035—we’re leading the au...
Compliance Ranges Comparison

Audi Stuttgart GmbH







BorgWarner






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

Audi Stuttgart GmbH

BorgWarner
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout