Comparison Overview
Pilgrim's
Pilgrim's
1770 Promontory Circle, None, Greeley, Colorado, US, 80634
Last Update: 29/01/2026
We are a global chicken and pork company. Eat proudly knowing the food on your dinner table is made with a commitment to be great-tasting, safe and sustainable - and we're only getting better.
Louis Dreyfus Company
Westblaak 92, Rotterdam, 3012 KM, NL
Last Update: 01/04/2026
Louis Dreyfus Company is a leading merchant and processor of agricultural goods. We leverage our global reach and extensive asset network to serve our customers and consumers around the world, delivering the right products to the right location, at the right time – safe...
Compliance Ranges Comparison
Pilgrim's
Louis Dreyfus Company
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for Pilgrim's in 2026.
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for Louis Dreyfus Company in 2026.
Incident History - Pilgrim's (X = Date, Y = Severity)
Pilgrim's cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Louis Dreyfus Company (X = Date, Y = Severity)
Louis Dreyfus Company cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Pilgrim's
Louis Dreyfus Company
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: *.*.