Comparison Overview
Naylors 

Naylors
Hollins Brook Way, Bury, England, BL9 8RR, GB
Last Update: 20/01/2026
Naylors is one of the UK’s leading equestrian retailers. We are a forward-looking, vibrant business operating in both the equestrian and countrywear retail sector. We currently have four stores; our flagship 15,000 sq ft superstore in Rochdale, stores in Nantwich, Canno...

Carrefour
93, Avenue de Paris, Massy, Île-de-France, FR, 91300
Last Update: 02/04/2026
The Carrefour Group: one of the world’s leading retailers In 50 years, the Carrefour Group has become a world leader in the retail sector. The second largest retailer in the world and the largest in Europe, the Group now features four major grocery retail formats: hy...
Compliance Ranges Comparison

Naylors







Carrefour






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Naylors in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Carrefour in 2026.
Incident History - Naylors (X = Date, Y = Severity)
Naylors cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Carrefour (X = Date, Y = Severity)
Carrefour cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Naylors

Carrefour
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.