Comparison Overview
Porsche Ukraine LLC
Porsche Ukraine LLC
Pavla Tychyny ave., 1 V , Kyiv, 02152, UA
Last Update: 21/01/2026
ТОВ «Порше Україна», дочірнє підприємство Porsche Holding Salzburg, є імпортером брендів Volkswagen, Volkswagen комерційні автомобілі, Audi, SEAT та CUPRA. Компанія імпортує автомобілі та запасні частини в Україну, реалізує продукцію брендів концерну та надає гарантійн...
Marelli
2 Chome-1917 Nisshincho, Kita Ward, Saitama City, 331-0823, JP
Last Update: 15/09/2026
Marelli is a global, independent technology partner to the automotive industry, with a strong and established track record in innovation and manufacturing excellence. As mobility is evolving fast and global trends drive unprecedented innovation, we leverage our expertis...
Compliance Ranges Comparison
Porsche Ukraine LLC
Marelli
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Porsche Ukraine LLC in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Marelli in 2026.
Incident History - Porsche Ukraine LLC (X = Date, Y = Severity)
Porsche Ukraine LLC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Marelli (X = Date, Y = Severity)
Marelli cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Porsche Ukraine LLC
Marelli
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.