Comparison Overview
ALDI SÜD

ALDI SÜD
Burgstraße 37, Mülheim an der Ruhr, 45476, DE
Last Update: 01/04/2026
Gemeinsam mit ALDI Nord gehören wir zu den führenden Discountern auf dem deutschen und internationalen Markt. Für mehr als 170.000 Kolleg:innen in 11 Ländern sind wir nicht nur Händler, sondern auch ein verlässlicher und verantwortungsvoller Arbeitgeber. Unsere Teams ...

Zalando
Valeska-Gert-Straße 5, Berlin, Berlin, DE, 10243
Last Update: 03/04/2026
Welcome to Zalando. Here’s some key info about us: Our position and vision: - We’re Europe’s leading online platform for fashion and lifestyle. - Founded in Berlin in 2008, we bring head-to-toe fashion to more than 50 million active customers in 25 markets; offering cl...
Compliance Ranges Comparison

ALDI SÜD







Zalando






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

ALDI SÜD

Zalando
FAQ
Latest Global CVEs
Fides is an open-source privacy engineering platform. From version 2.33.0 to before version 2.84.5, there is a DOM-based XSS vulnerability in fides.js via the fides_description override. This issue has been patched in version 2.84.5.
WACRM prior to commit 73041bf contain an authorization bypass vulnerability in the automation engine that allows authenticated attackers to access and modify contacts belonging to other tenants by supplying an arbitrary caller-controlled contact_id in the POST request body without tenant ownership verification. Attackers can exploit the service-role client that bypasses row-level security to modify victim contact fields including name, email, and company across tenant boundaries using only a known contact UUID.
Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
When ALLOW_INSECURE_RAW_TEXT is enabled, whitespace-variant closing tags (e.g., </style\t>) are not recognized by the sanitizer but accepted by browsers as valid end tags, allowing subsequent content to escape sanitization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
Headplane is a feature-complete Web UI for Headscale. Prior to versions 0.6.3 and 0.7.0-beta.3, Headplane was vulnerable to a path traversal / authorization bypass in the Headscale API client used by node and user rename operations. This issue has been patched in versions 0.6.3 and 0.7.0-beta.3.