Comparison Overview
AB InBev Japan, New Zealand
AB InBev Japan, New Zealand
2-24-12 Shibuya, Shibuya-ku, Tokyo, 150-6139, JP
Last Update: 24/02/2026
We are a company of owners. We believe that you get out what you put in. We strive to be the best. Pursuing our Dream, committed to improving lives for more people in more communities. For centuries, we’ve been bringing people together, through sports, through music a...
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...
Compliance Ranges Comparison
AB InBev Japan, New Zealand
Coca-Cola HBC
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for AB InBev Japan, New Zealand in 2026.
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Coca-Cola HBC in 2026.
Incident History - AB InBev Japan, New Zealand (X = Date, Y = Severity)
AB InBev Japan, New Zealand cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Coca-Cola HBC (X = Date, Y = Severity)
Coca-Cola HBC cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
AB InBev Japan, New Zealand
Coca-Cola HBC
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)