Comparison Overview
Coca-Cola Beverages Uganda
Coca-Cola Beverages Uganda
Plot 964 Kyaggwe, Namanve Industrial Area, Jinja Road, Kampala, UG
Last Update: 30/03/2026
Coca-Cola Beverages Africa (CCBA) in Uganda bottles some of the world's iconic non-alcoholic ready-to-drink beverages at its Century and Rwenzori Bottling plants in Namanve and Mbarara. Our products include carbonated soft drinks (sodas), juices under the Minute Maid b...
Coca-Cola HBC
Turmstrasse 30, Zug, 6300, CH
Last Update: 11/06/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
Coca-Cola Beverages Uganda
Coca-Cola HBC
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Coca-Cola Beverages Uganda in 2026.
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Coca-Cola HBC in 2026.
Incident History - Coca-Cola Beverages Uganda (X = Date, Y = Severity)
Coca-Cola Beverages Uganda 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
Coca-Cola Beverages Uganda
Coca-Cola HBC
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.