Comparison Overview
Beverage Coding

Beverage Coding
N/A
Last Update: 31/01/2026
Linx Printing Technology has a wide range of solutions to help those working in the beverage industry. Find out more about how they can use their over 25 years of experience to help you!

The Coca-Cola Company
One Coca-Cola Plaza, Atlanta, 30313, US
Last Update: 12/09/2026
From our roots at the counter of a local Atlanta pharmacy, to our current portfolio of more than 200 beverages, The Coca-Cola Company is one of the most globally-recognized brands in the world. Today, our lineup features beloved beverage brands, including Coca-Cola, S...
Compliance Ranges Comparison

Beverage Coding







The Coca-Cola Company






Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Beverage Coding in 2026.
Incidents vs Food and Beverage Services Industry Avg (This Year)
The Coca-Cola Company has 96.08% more incidents than the average of all companies with at least one recorded incident.
Incident History - Beverage Coding (X = Date, Y = Severity)
Beverage Coding cyber incidents detection timeline including parent company and subsidiaries.
Incident History - The Coca-Cola Company (X = Date, Y = Severity)
The Coca-Cola Company cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Beverage Coding

The Coca-Cola Company
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)