Comparison Overview
Marks and Spencer
Marks and Spencer
Waterside House, London, W2 1NW, GB
Last Update: 06/09/2026
At M&S, we're dedicated to being the most trusted retailer, prioritising quality and delivering value. Every day, we bring the magic of M&S to our customers, whenever, wherever and however they want to shop with us. For over a century, we've set the standard, doing the ...
Jumbo Supermarkten
Rijksweg 15, Veghel, 5462 CE, NL
Last Update: 07/09/2026
Jumbo is een Brabants familiebedrijf met een rijke historie. Begonnen in 1921 als levensmiddelengroothandel heeft Jumbo een indrukwekkende groei doorgemaakt. Inmiddels is het de tweede supermarktketen van Nederland. Wekelijks verwelkomt Jumbo miljoenen klanten in meer d...
Compliance Ranges Comparison
Marks and Spencer
Jumbo Supermarkten
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
Marks and Spencer has 288.89% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Jumbo Supermarkten in 2026.
Incident History - Marks and Spencer (X = Date, Y = Severity)
Marks and Spencer cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Jumbo Supermarkten (X = Date, Y = Severity)
Jumbo Supermarkten cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Marks and Spencer
Jumbo Supermarkten
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.