Comparison Overview
Coca-Cola HBC

Coca-Cola HBC
Turmstrasse 30, Zug, 6300, CH
Last Update: 14/09/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...

JDE Peet's
Oosterdoksstraat 80, Amsterdam, North Holland, NL, 1011 DK
Last Update: 18/09/2026
JDE Peet’s is the world’s leading pure-play coffee company, serving approximately 4,400 cups of coffee per second in more than 100 markets. Guided by our ‘Reignite the Amazing’ strategy, we are focusing on brand-led growth across three big bets: Peet’s, L’OR, and Jacobs...
Compliance Ranges Comparison

Coca-Cola HBC







JDE Peet's






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 JDE Peet's 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 - JDE Peet's (X = Date, Y = Severity)
JDE Peet's cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Coca-Cola HBC

JDE Peet's
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)