Comparison Overview
Footpatrol
Footpatrol
80 Berwick Street, London, W1F 8, GB
Last Update: 27/02/2026
The UK's original and world renowned destination sneaker store, Footpatrol originally opened in 2002 and relocated to the current store location in 2010. Always at the heart of supplying the global culture with the most desirable footwear, apparel and accessories, Footp...
SEPHORA
Neuilly sur Seine, 92576 , FR
Last Update: 08/09/2026
Sephora is the world’s leading global prestige beauty retail brand. With our curation of more than 500 brands and our own label, Sephora Collection, we offer the most unique and diverse range of prestige beauty products, tailored to our customers’ needs from fragrance t...
Compliance Ranges Comparison
Footpatrol
SEPHORA
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Footpatrol in 2026.
Incidents vs Retail Industry Avg (This Year)
SEPHORA has 94.17% more incidents than the average of all companies with at least one recorded incident.
Incident History - Footpatrol (X = Date, Y = Severity)
Footpatrol cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SEPHORA (X = Date, Y = Severity)
SEPHORA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Footpatrol
SEPHORA
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.