Comparison Overview
Grupo Chedraui

Grupo Chedraui
Av. Constituyentes, CDMX, CDMX, 11950, MX
Last Update: 02/04/2026
Grupo Chedraui es un súper mexicano con más de 50 años de historia en el país y en Estados Unidos; se fundó en la década de los años veinte en la ciudad de Xalapa, Veracruz, con un establecimiento llamado “Al Puerto de Beirut”. Posteriormente en el año de 1927, “Al Puer...

Ross Stores, Inc.
5130 Hacienda Drive, Dublin, CA, US, 94568
Last Update: 10/07/2026
For the last 40+ years, Ross Stores, Inc. has grown from a six-store chain into an $21.1 billion, Fortune 500 Company. We operate our off-price businesses in a way that keeps costs low so we can pass the savings to our customers. We continue to open new stores and our s...
Compliance Ranges Comparison

Grupo Chedraui







Ross Stores, Inc.






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

Grupo Chedraui

Ross Stores, Inc.
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.