Comparison Overview
OXXO

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

Aldi UK
Aldi Stores Ltd, Atherstone, CV9 2SQ, GB
Last Update: 01/04/2026
Since arriving in the UK in 1990, we’ve gone on to be one of the biggest (and the highest-paying) supermarkets in the game, with a team of 45,000 colleagues who make Everyday Amazing. We've been crowned the 'Retail Employer of the Year' at the Grocer Gold Awards four t...
Compliance Ranges Comparison

OXXO







Aldi UK






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

OXXO

Aldi UK
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.