Comparison Overview
Reliance Retail

Reliance Retail
Reliance Corporate Park, Mumbai, IN
Last Update: 05/04/2026
Reliance Retail is the retail initiative of RIL and an epicentre of our consumer-facing businesses. It has been ranked as the fastest-growing retailer in the world. It is ranked 53rd in the list of Top Global Retailers and is the only Indian Retailer to feature in the T...

Publix Super Markets
3300 Publix Corporate Parkway, Lakeland, 33811, US
Last Update: 01/04/2026
Founded in 1930, Publix Super Markets is the largest and fastest-growing employee-owned supermarket chain in the United States. Publix employs over 200,000 associates. We are privately-owned, hold no long-term debt, have avoided layoffs, and continue to grow year after ...
Compliance Ranges Comparison

Reliance Retail







Publix Super Markets






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

Reliance Retail

Publix Super Markets
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.