Comparison Overview
Tesco Technology

Tesco Technology
85 Clerkenwell Road, London, EC1R 5AR, GB
Last Update: 02/04/2026
We are Tesco, and we’re always looking ahead. We use tech to make things a little better for everyone, every day. Forget off- the-shelf. We love coming up with our own ideas and building things ourselves. We empower our technologists to play a part in Tesco’s future...

ALDI Nord Group
16 Eckenbergstr., Essen, Ruhr, DE, 45307
Last Update: 01/04/2026
Welcome to the ALDI Nord Group! The ALDI Nord Group is one of the leading international retail enterprises. With a tradition stretching back over 110 years, the ALDI brand is synonymous with the invention of discount retail. ALDI Nord focuses on the essentials and re...
Compliance Ranges Comparison

Tesco Technology







ALDI Nord Group






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

Tesco Technology

ALDI Nord Group
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.