Comparison Overview
Nordzucker Deutschland
Nordzucker Deutschland
Küchenstraße, Brunswick, 38100, DE
Last Update: 10/06/2026
Nordzucker ist einer der weltweit führenden Hersteller von Zucker aus Rübe und Rohr. Wir sind stolz darauf, Menschen mit einem Lebensmittel zu versorgen, das im Einklang mit der Natur und unter hohen Sozial- und Qualitätsstandards hergestellt wird. Unser Team mit über...
Cargill
15407 McGinty Rd W, Wayzata, 55391, US
Last Update: 04/04/2026
Cargill is a family company committed to nourishing the world in a safe, responsible and sustainable way. With over 158 years of experience, we sit at the heart of the supply chain, partnering with producers and customers to source, make and deliver products that are vi...
Compliance Ranges Comparison
Nordzucker Deutschland
Cargill
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for Nordzucker Deutschland in 2026.
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for Cargill in 2026.
Incident History - Nordzucker Deutschland (X = Date, Y = Severity)
Nordzucker Deutschland cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Cargill (X = Date, Y = Severity)
Cargill cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Nordzucker Deutschland
Cargill
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: *.*.