Comparison Overview
Alicorp
Alicorp
Avenida 28 de Julio 1150, Miraflores, Piso 6, Miraflores, Lima, PE, 15047
Last Update: 19/03/2026
We are a leading consumer goods company in the Peruvian market, with operations in six countries in America—Peru, Bolivia, Ecuador, Chile, Colombia, and EEUU—where we manage over 150 of our own brands. We are dedicated to improving families’ quality of life and providi...
Danone
17 boulevard Haussmann, Paris, 75000, FR
Last Update: 01/04/2026
Danone is a leading global food and beverage company operating in three health-focused, fast-growing, and on-trend Categories: Essential Dairy & Plant-Based products, Waters, and Specialized Nutrition. With a long-standing mission of bringing health through food to as...
Compliance Ranges Comparison
Alicorp
Danone
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for Alicorp in 2026.
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for Danone in 2026.
Incident History - Alicorp (X = Date, Y = Severity)
Alicorp cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Danone (X = Date, Y = Severity)
Danone cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Alicorp
Danone
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: *.*.