Comparison Overview
Vero Moda

Vero Moda
Inge Lehmanns Gade Aarhus C, Middle Jutland 8000, DK
Last Update: 12/05/2026
Since 1987, VERO MODA has been present in the mind of stylish young women looking for new trends, accessible styles and fashionable must-have items. Our trademark is a vibrant and accessible approach to fashion. We are one of the most experienced international players ...

Magalu
Rua Maria Prestes Maia 300, SAO PAULO, SP, BR, 02047-901
Last Update: 28/03/2026
O Magalu é o maior ecossistema para comprar e vender no Brasil, uma plataforma digital, com pontos físicos e calor humano. Desde maio de 2011, a companhia é listada no Novo Mercado da B3. Nos últimos anos, fez 14 aquisições, consolidando sua presença nacional. Além de...
Compliance Ranges Comparison

Vero Moda







Magalu






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

Vero Moda

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