Comparison Overview
Molson Coors BH
Molson Coors BH
Ulica Braće Podgornika 4/E, Banja Luka, 78 000, BA
Last Update: 20/04/2026
Molson Coors BH d.o.o. je firma osnovana 2011. sa sjedištem u Banja Luci. Glavne su joj aktivnosti podrška prodajnim i marketing aktivnostima pivskih brendova naših pivara prvenstveno iz Srbije (Apatinska pivara - Jelen), Hrvatske (Zagrebačka pivara - Ožujsko) i Crne Go...
Ambev
São Paulo, São Paulo, 04530-001, BR
Last Update: 29/06/2026
Hey there! Welcome. Here at Ambev, there are lots of people and amazing projects beyond our labels! Let’s talk about that. We believe that having a big dream requires just the same effort as having a small one. That is why our big dream began back in the 1880s, with...
Compliance Ranges Comparison
Molson Coors BH
Ambev
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Molson Coors BH in 2026.
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Ambev in 2026.
Incident History - Molson Coors BH (X = Date, Y = Severity)
Molson Coors BH cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Ambev (X = Date, Y = Severity)
Ambev cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Molson Coors BH
Ambev
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: *.*.