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

Next
Enderby, Leicester, Leicestershire, GB, LE19 4AT
Last Update: 06/09/2026
At Next we never underestimate what we can do. Bring your energy, play to your strengths and never shy away from change. Push yourself and back others. Make things happen that will be bigger and better than before. Come and work for one of the UK’s biggest retailers. ...
Compliance Ranges Comparison

ALDI SÜD







Next






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 Next 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 - Next (X = Date, Y = Severity)
Next cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

ALDI SÜD

Next
FAQ
Latest Global CVEs
Netskope was notified about a potential gap in Netskope Endpoint DLP (EPDLP) running on Windows systems. Successful exploitation of the gap could potentially allow a privileged user to send a crafted message to the EPDLP process port to trigger an integer overflow, leading to memory corruption. Successful exploitation would require the EPDLP module to be enabled in the client configuration, and that Memory Integrity is disabled. A successful exploit could potentially result in a denial-of-service, arbitrary code execution, or privilege escalation on the local machine.
Netskope was notified of an out-of-bounds heap read affecting the Endpoint DLP (EPDLP) service of the Netskope Client. A local standard user could potentially send a specially crafted message that is not properly validated with a bounds check, likely crashing the kernel driver handler. Successful exploitation could potentially crash the EPDLP service, temporarily interrupting DLP enforcement. A successful exploit could potentially also reveal per-boot memory layout information to unauthorized users.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 is vulnerable to a denial of service where a specific functionality on a Db2 server can be disabled by a privileged user under certain conditions.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 could allow an attacker with the ability to control or impersonate a DRDA server endpoint to execute arbitrary commands on Db2 clients due to a stack-based buffer overflow that improperly copies user-controlled data into a fixed-size stack buffer without bounds checking.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 could allow an authenticated user to send a specially crafted request to write arbitrary files on the system.