Comparison Overview
Bata Italy

Bata Italy
Via Alessandro Volta, 6 Limena, Padova 35010, IT
Last Update: 27/10/2025
Il Gruppo Bata è il primo retailer mondiale per la produzione e commercializzazione di calzature. Fondato nel 1894 in Repubblica Ceca, è presente in più di 70 paesi in tutto il mondo con un network di oltre 5300 punti vendita. Dal 1931 Bata in Italia è Compar S.p...

Inditex
Avda. de la Diputación s/n, Arteixo, 15143, ES
Last Update: 09/08/2026
What is Inditex? Inditex comprises seven brands: Zara, Pull&Bear, Massimo Dutti, Bershka, Stradivarius, Oysho and Zara Home. We sell in 213 markets through our online platforms and our over 5.800 stores. But… What is Inditex? We are the clothes you choose to wear, th...
Compliance Ranges Comparison

Bata Italy







Inditex






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

Bata Italy

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