Comparison Overview
Louis Vuitton
Louis Vuitton
2 Rue du Pont Neuf, Paris, 75001, FR
Last Update: 05/09/2026
For more than 150 years, men and women at Louis Vuitton have shared the same spirit of excellence and passion, reaffirming their expertise every day, the world over. With us, every career is a journey, filled with excitement and challenge, desire and daring. There is no...
Prada Group
Via Antonio Fogazzaro, 28, Milan , 20135, IT
Last Update: 05/09/2026
Pioneer of a dialogue with contemporary society across diverse cultural spheres and an influential leader in luxury fashion, Prada Group founds its identity on essential values such as creative independence, transformation, and sustainable development, offering its bran...
Compliance Ranges Comparison
Louis Vuitton
Prada Group
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
Louis Vuitton has 37.5% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
No incidents recorded for Prada Group in 2026.
Incident History - Louis Vuitton (X = Date, Y = Severity)
Louis Vuitton cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Prada Group (X = Date, Y = Severity)
Prada Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Louis Vuitton
Prada Group
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.