Comparison Overview
Dole plc

Dole plc
29 North Anne Street, Dublin, IE
Last Update: 29/06/2026
In Dole plc we are, first & foremost, fresh produce enthusiasts. The world’s leading fresh produce provider, we market the most nutritious of products with the lowest environmental impact. Operating out of 30 countries, while serving many more, our vertically integrat...

Alfa Corporativo
Ave. Gómez Morín 1111, San Pedro Garza García, 66254, MX
Last Update: 01/04/2026
Sigma Foods es una empresa multinacional líder en alimentos empacados, con un portafolio de más de 100 marcas y operaciones en 17 países. Atendemos más de 640,000 puntos de venta con el apoyo de 47,000 colaboradores, 64 plantas de producción y 189 centros de distribució...
Compliance Ranges Comparison

Dole plc







Alfa Corporativo






Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for Dole plc in 2026.
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for Alfa Corporativo in 2026.
Incident History - Dole plc (X = Date, Y = Severity)
Dole plc cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Alfa Corporativo (X = Date, Y = Severity)
Alfa Corporativo cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Dole plc

Alfa Corporativo
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: *.*.