Comparison Overview
Asahi Europe & International
Asahi Europe & International
88 - 100 Chertsey Road, Woking, Surrey, GB, GU21 5BJ
Last Update: 30/12/2025
We are Asahi Europe & International (AEI), part of Asahi Group Holdings, a leading global beer, spirits, soft drinks and food group listed on the Tokyo Stock Exchange. With a rich history we have an extensive footprint across Europe and run 19 production facilities acro...
PepsiCo
700 Anderson Hill Road, Purchase, 10577, US
Last Update: 06/07/2026
PepsiCo is a playground for curious people. We invite thinkers, doers, and changemakers to champion innovation, take calculated risks, and challenge the status quo. From executives to team members on the front lines, we’re excited about the future. We take chances. Toge...
Compliance Ranges Comparison
Asahi Europe & International
PepsiCo
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Asahi Europe & International in 2026.
Incidents vs Food and Beverage Services Industry Avg (This Year)
PepsiCo has 88.68% more incidents than the average of all companies with at least one recorded incident.
Incident History - Asahi Europe & International (X = Date, Y = Severity)
Asahi Europe & International cyber incidents detection timeline including parent company and subsidiaries.
Incident History - PepsiCo (X = Date, Y = Severity)
PepsiCo cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Asahi Europe & International
PepsiCo
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: *.*.