Comparison Overview
Coca-Cola HBC

Coca-Cola HBC
Turmstrasse 30, Zug, 6300, CH
Last Update: 13/07/2026
We bottle and sell the beverages of The Coca-Cola Company exclusively in our 29 markets and partner with other beverage businesses to also sell their brands. With over 100 brands covering eight categories – sparkling, water, juices, ready-to-drink tea, energy, plant-bas...

US Foods
9399 W. Higgins Rd., Suite 500, Rosemont, IL, US, 60018
Last Update: 25/07/2026
US Foods is one of America’s great food companies and a leading foodservice distributor, partnering with approximately 300,000 restaurants and foodservice operators to help their businesses succeed. With 28,000 associates and more than 70 locations, US Foods provides ...
Compliance Ranges Comparison

Coca-Cola HBC







US Foods






Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Coca-Cola HBC in 2026.
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for US Foods in 2026.
Incident History - Coca-Cola HBC (X = Date, Y = Severity)
Coca-Cola HBC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - US Foods (X = Date, Y = Severity)
US Foods cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Coca-Cola HBC

US Foods
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.