Comparison Overview
Lidl International
Lidl International
Stiftsbergstraße 1, Neckarsulm, DE
Last Update: 13/07/2026
Welcome to Lidl International! 🌎 About 375,000 employees, over 31 countries worldwide, 1 global #teamlidl We have built up a community during more than 40 years of our Lidl journey. And #teamlidl with about 375,000 employees is growing every day. Worldwide. Get a ...
Landmark Group
Dubai, AE
Last Update: 13/09/2026
For over five decades, Landmark Group has shaped the region’s retail and hospitality landscape-growing from a single store in Bahrain to one of the largest and most successful omnichannel and hospitality groups across the Middle East, Asia and Africa. Rooted in purpose...
Compliance Ranges Comparison
Lidl International
Landmark Group
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
Lidl International has 11.11% 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 Landmark Group in 2026.
Incident History - Lidl International (X = Date, Y = Severity)
Lidl International cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Landmark Group (X = Date, Y = Severity)
Landmark Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Lidl International
Landmark Group
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.