Comparison Overview
Walgreens Boots Alliance

Walgreens Boots Alliance
108 Wilmot Road, Deerfield, IL, US, 60015
Last Update: 02/04/2026
Walgreens Boots Alliance (Nasdaq: WBA) is an integrated healthcare, pharmacy and retail leader serving millions of customers and patients every day, with a 170-year heritage of caring for communities. A trusted, global innovator in retail pharmacy with more than 12,500...

CVS Pharmacy
1 CVS Drive, Woonsocket, 02895, US
Last Update: 23/07/2026
CVS Pharmacy is a leading U.S. retail pharmacy and a subsidiary of CVS Health. CVS Pharmacy operates thousands of neighborhood locations across the United States, providing prescription medications, over‑the‑counter health products, and everyday essentials. Many CVS Pha...
Compliance Ranges Comparison

Walgreens Boots Alliance







CVS Pharmacy






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

Walgreens Boots Alliance

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