Comparison Overview
Lojas Renner S.A.
Lojas Renner S.A.
Av. Joaquim Porto Villanova, 401, Porto Alegre, Rio Grande do Sul, BR, 91410400
Last Update: 14/09/2026
We are a fashion and lifestyle ecosystem connected to our customers through digital channels and more than 600 stores in Brazil, Argentina and Uruguay. From the beginning, everything we do is to enchant. This is how our story began, in 1965, conquering important milesto...
Esselunga
Via Giambologna 1, Limito di Pioltello, 20096, IT
Last Update: 13/09/2026
Esselunga è una delle principali catene italiane nel settore della grande distribuzione. La sua storia inizia nel 1957 con l'apertura a Milano del primo supermercato in Italia; oggi, attraverso una rete di oltre 180 negozi, il gruppo è presente in Lombardia, Toscana, Em...
Compliance Ranges Comparison
Lojas Renner S.A.
Esselunga
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Lojas Renner S.A. in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Esselunga in 2026.
Incident History - Lojas Renner S.A. (X = Date, Y = Severity)
Lojas Renner S.A. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Esselunga (X = Date, Y = Severity)
Esselunga cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Lojas Renner S.A.
Esselunga
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.