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, ...
Stellantis
Amsterdam, NL
Last Update: 10/09/2026
Our storied and iconic brands embody the passion of their visionary founders and today’s customers in their innovative products and services: they include Abarth, Alfa Romeo, Chrysler, Citroën, Dodge, DS Automobiles, Fiat, Jeep®, Lancia, Maserati, Opel, Peugeot, Ram, Va...
Compliance Ranges Comparison
OTOKAR Otomotiv ve Savunma Sanayi A.Ş.
Stellantis
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 Stellantis 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 - Stellantis (X = Date, Y = Severity)
Stellantis cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
OTOKAR Otomotiv ve Savunma Sanayi A.Ş.
Stellantis
FAQ
Latest Global CVEs
vLLM through 0.29.0 fails to properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/push_worker.py#L162-L181
- https://github.com/vllm-project/vllm/pull/55677
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-rejected-requests
redis-parser through 3.0.0 contains a denial of service vulnerability in the RESP protocol parser that allows malicious Redis endpoints to crash the client process through unbounded recursion on nested arrays. Attackers can send crafted RESP byte streams with repeated array headers that exhaust the V8 call stack, causing an uncaught RangeError that terminates the Node.js process without triggering error handling callbacks.
- https://github.com/NodeRedis/node-redis-parser
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L204-L213
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L291-L306
- https://github.com/redis/ioredis/issues/2108
- https://www.vulncheck.com/advisories/redis-parser-through-3.0.0-denial-of-service-via-unbounded-recursion
Improper neutralization of special elements in output used by a downstream component ('injection') in Azure Cosmos DB allows an authorized attacker to elevate privileges over a network.
Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.