Comparison Overview
ALDI SÜD

ALDI SÜD
Burgstraße 37, Mülheim an der Ruhr, 45476, DE
Last Update: 01/04/2026
Gemeinsam mit ALDI Nord gehören wir zu den führenden Discountern auf dem deutschen und internationalen Markt. Für mehr als 170.000 Kolleg:innen in 11 Ländern sind wir nicht nur Händler, sondern auch ein verlässlicher und verantwortungsvoller Arbeitgeber. Unsere Teams ...

Big Lots
4900 E Dublin Granville Rd, Columbus, US
Last Update: 10/09/2026
Big Lots is an off-price retailer, offering bargains on everything for the home, including furniture, décor, pantry essentials, kitchenware, pet supplies, and more. Big Lots fulfills its mission to help customers "Live Big and Save Lots" by strategically sourcing barga...
Compliance Ranges Comparison

ALDI SÜD







Big Lots






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

ALDI SÜD

Big Lots
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.