Comparison Overview
Coca-Cola Southwest Beverages

Coca-Cola Southwest Beverages
5240 Lyndon B Johnson Fwy, Dallas, 75240, US
Last Update: 26/04/2026
Dallas-based Coca-Cola Southwest Beverages (CCSWB), a company of Arca Continental, is one of the largest Coca-Cola bottlers in the United States. CCSWB produces, markets and distributes Coca-Cola brands in Texas and parts of New Mexico, Oklahoma and Arkansas.

Carlsberg Group
J.C. Jacobsens Gade, København V, Hovedstaden, DK, 1799
Last Update: 13/07/2026
This is the official LinkedIn channel of the Carlsberg Group. The Carlsberg Group was established in 1847 by brewer J.C. Jacobsen. J.C. Jacobsen was a true renaissance man. A believer in quality, research and serving the community, he shared his knowledge with fellow b...
Compliance Ranges Comparison

Coca-Cola Southwest Beverages







Carlsberg Group






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

Coca-Cola Southwest Beverages

Carlsberg Group
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.