Comparison Overview
OTOKAR Otomotiv ve Savunma Sanayi A.Ş.
OTOKAR Otomotiv ve Savunma Sanayi A.Ş.
Atatürk Caddesi No:6 , Sakarya, undefined, 54580, TR
Last Update: 24/01/2026
Koç Topluluğu şirketlerinden Otokar, 1963'ten bu yana kendi teknoloji, tasarım ve uygulamaları ile müşterilerinin ihtiyaçlarına uygun özel çözümler sunuyor. Sakarya’daki 552.000 m²’lik alana kurulu fabrikasında 4000’den fazla çalışanıyla faaliyet gösteriyor. Otokar, ...
Porsche AG
Porscheplatz 1, Stuttgart, D-70435, DE
Last Update: 13/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
OTOKAR Otomotiv ve Savunma Sanayi A.Ş.
Porsche AG
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for OTOKAR Otomotiv ve Savunma Sanayi A.Ş. in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Porsche AG in 2026.
Incident History - OTOKAR Otomotiv ve Savunma Sanayi A.Ş. (X = Date, Y = Severity)
OTOKAR Otomotiv ve Savunma Sanayi A.Ş. 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
OTOKAR Otomotiv ve Savunma Sanayi A.Ş.
Porsche AG
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