Comparison Overview
Tesco
Tesco
Shire Park, Welwyn Garden City, AL7 1GA, GB
Last Update: 11/09/2026
One of the world’s largest retailers of consumer goods from food to fashion. Serving our customers, communities and planet a little better every day in our stores and online is at the heart of everything we do. Founded in 1919 by Jack Cohen using the £30 he received on...
OXXO
Edison #1235 Nte., Monterrey, 64480, MX
Last Update: 02/04/2026
Somos la cadena de tiendas de conveniencia más grande de México y América Latina, con 45 años de experiencia y más de 22 mil establecimientos ubicados a lo largo de la República Mexicana, Colombia, Perú, Chile y Brasil. En OXXO como compañía 100% mexicana y como parte ...
Compliance Ranges Comparison
Tesco
OXXO
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
Tesco has 44.44% fewer 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 OXXO in 2026.
Incident History - Tesco (X = Date, Y = Severity)
Tesco cyber incidents detection timeline including parent company and subsidiaries.
Incident History - OXXO (X = Date, Y = Severity)
OXXO cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Tesco
OXXO
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.