Comparison Overview
TESCO STORES SR, a. s.

TESCO STORES SR, a. s.
Cesta na Senec 2, Bratislava, 81561, SK
Last Update: 12/05/2026
Spoločnosť TESCO STORES SR, a.s. vstúpila na slovenský trh v roku 1996 a v súčasnosti prevádzkuje viac ako 150 obchodov rôznych formátov - od formátov Extra, cez hypermarkety, supermarkety a expresy. Prevádzkuje na Slovensku 3 distribučné centrá v Beckove, Gáni a v Pre...

Walmart
702 SW 8th St, Bentonville, Arkansas, US, 72712
Last Update: 29/07/2026
More than 60 years ago, Sam Walton opened the first Walmart in Rogers, Arkansas. Today, we’re a people-led, tech-powered omnichannel retailer dedicated to helping people save money and live better all around the world. Our 2.1 million associates are the engine behind w...
Compliance Ranges Comparison

TESCO STORES SR, a. s.







Walmart






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for TESCO STORES SR, a. s. in 2026.
Incidents vs Retail Industry Avg (This Year)
Walmart has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - TESCO STORES SR, a. s. (X = Date, Y = Severity)
TESCO STORES SR, a. s. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Walmart (X = Date, Y = Severity)
Walmart cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

TESCO STORES SR, a. s.

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