Comparison Overview
Keurig Dr Pepper Canada

Keurig Dr Pepper Canada
3700 Rue Jean-Rivard, Montréal, CA
Last Update: 20/12/2025
Keurig Dr Pepper Canada is a leading beverage company, with a portfolio of more than 70 owned, licensed, and partner brands and powerful distribution capabilities to provide a beverage for every need, anytime, anywhere. We hold leadership positions in categories includi...

Essity
Klarabergsviadukten 63, Stockholm, SE
Last Update: 02/04/2026
Essity - a globally leading hygiene and health company. Our expertise in hygiene and health began with the acquisition of the Swedish company Mölnlycke in 1975, through which our roots stretch back to 1849. Today, our sustainable innovations from globally trusted brands...
Compliance Ranges Comparison

Keurig Dr Pepper Canada







Essity






Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Keurig Dr Pepper Canada in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Essity in 2026.
Incident History - Keurig Dr Pepper Canada (X = Date, Y = Severity)
Keurig Dr Pepper Canada cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Essity (X = Date, Y = Severity)
Essity cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Keurig Dr Pepper Canada

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