Comparison Overview
Jean Paul GAULTIER
Jean Paul GAULTIER
325 rue Saint-Martin, PARIS, FR
Last Update: 07/02/2026
Fondée par son créateur éponyme en 1976, la maison Jean Paul Gaultier est un paradoxe parisien – mêlant les codes du style français à une rébellion iconoclaste, la qualité de la couture à une sensibilité urbaine, le choc au chic. Réputé pour son tailoring audacieux et...
LVMH
22, avenue Montaigne, Paris, 75008, FR
Last Update: 11/09/2026
LVMH is the world leader in luxury. A family group founded in 1987 and headed by Chairman and CEO Bernard Arnault, LVMH is now home to 75 iconic Maisons, which embody a distinctive art de vivre blending heritage and modernity. With reported sales of 86.2 billion euros ...
Compliance Ranges Comparison
Jean Paul GAULTIER
LVMH
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
No incidents recorded for Jean Paul GAULTIER in 2026.
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
LVMH has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Jean Paul GAULTIER (X = Date, Y = Severity)
Jean Paul GAULTIER cyber incidents detection timeline including parent company and subsidiaries.
Incident History - LVMH (X = Date, Y = Severity)
LVMH cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Jean Paul GAULTIER
LVMH
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.