Comparison Overview
Bata Chile

Bata Chile
Maipu, Santiago, Region Metropolitana 7591538, CL
Last Update: 23/04/2026
Bata es una empresa global con actividades en los cinco continentes controlada por cuatro Unidades Regionales de Negocios Comerciales (CBUs). Cada una de estas unidades se especializa en la región de tareas específicas, tales como el desarrollo de productos, compras, o ...

Aditya Birla Fashion and Retail Ltd.
Piramal Agastya Corporate Park, Building 'A', 4th and 5th Floor, Unit No. 401, 403, 501, 502, L.B.S. Road, Kurla, Mumbai, Maharashtra, IN, 400070
Last Update: 31/03/2026
Aditya Birla Fashion and Retail Limited (ABFRL), part of the Aditya Birla Group, is India’s leading fashion powerhouse, offering a distinguished portfolio of renowned brands and retail formats, catering to multiple high-growth segments. As of March 31, 2025, the Compan...
Compliance Ranges Comparison

Bata Chile







Aditya Birla Fashion and Retail Ltd.






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
No incidents recorded for Bata Chile in 2026.
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
No incidents recorded for Aditya Birla Fashion and Retail Ltd. in 2026.
Incident History - Bata Chile (X = Date, Y = Severity)
Bata Chile cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Aditya Birla Fashion and Retail Ltd. (X = Date, Y = Severity)
Aditya Birla Fashion and Retail Ltd. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Bata Chile

Aditya Birla Fashion and Retail Ltd.
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.