Comparison Overview
Barilla Group
Barilla Group
Via Mantova, 166, Parma, 43122, IT
Last Update: 09/03/2026
We are an Italian family-owned food company. And like all Italian families, we take food very seriously. We have been doing this for 148 years. Today we are committed to bringing people closer to the joy of good food and making quality the choice for a better life, from...
ADM
77 W Wacker Dr, Chicago, 60601, US
Last Update: 29/03/2026
ADM unlocks the power of nature to enrich the quality of life. We’re an essential global agricultural supply chain manager and processor, providing food security by connecting local needs with global capabilities. We’re a premier human and animal nutrition provider, off...
Compliance Ranges Comparison
Barilla Group
ADM
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for Barilla Group in 2026.
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for ADM in 2026.
Incident History - Barilla Group (X = Date, Y = Severity)
Barilla Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ADM (X = Date, Y = Severity)
ADM cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Barilla Group
ADM
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: *.*.