Comparison Overview
BRAC-Aarong

BRAC-Aarong
346 Tejgaon Industrial Area, Dhaka, undefined, 1208, BD
Last Update: 07/03/2026
Aarong is Bangladesh’s most popular lifestyle retail chain. This ethical brand began in 1978 as a humble means to empower rural artisans to rise above poverty. Today, with 28 retail stores across Bangladesh and over 100 fashion and lifestyle product lines, Aarong suppor...

Tesco
Shire Park, Welwyn Garden City, AL7 1GA, GB
Last Update: 12/08/2026
One of the world’s largest retailers of consumer goods from food to fashion. Serving our customers, communities and planet a little better every day in our stores and online is at the heart of everything we do. Founded in 1919 by Jack Cohen using the £30 he received on...
Compliance Ranges Comparison

BRAC-Aarong







Tesco






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for BRAC-Aarong in 2026.
Incidents vs Retail Industry Avg (This Year)
Tesco has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - BRAC-Aarong (X = Date, Y = Severity)
BRAC-Aarong cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Tesco (X = Date, Y = Severity)
Tesco cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

BRAC-Aarong

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