Comparison Overview
Starbucks India

Starbucks India
Andheri, None, Mumbai, Maharashtra, IN, 400059
Last Update: 12/03/2026
Starbucks India By bringing people together over coffee, Starbucks has become one of the world’s best-known and best-loved companies. We purchase, roast and serve award-winning coffee. We also offer Italian-style espresso beverages, cold blended beverages, delicious f...

Boots UK
1 Thane Road, Nottingham, NG90 1BS, GB
Last Update: 02/04/2026
Boots is the UK’s leading health and beauty retailer with over 52,000 team members and around 1,800 stores,* ranging from local community pharmacies to large destination health and beauty stores. We serve our customers and patients’ wellbeing for life as the leading pr...
Compliance Ranges Comparison

Starbucks India







Boots UK






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

Starbucks India

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