Comparison Overview
Tulip Food Company
Tulip Food Company
Tulipvej 1, Randers SV, 8940, DK
Last Update: 02/04/2026
Tulip Food Company har skiftet navn til Danish Crown Foods. Du kan følge med på vores nye side her: https://www.linkedin.com/company/danish-crown-foods/ *** Tulip Food Company has changes its name to Danish Crown Foods. You can follow ud on our new company page here: ...
Mars
6885 Elm St, McLean, Virginia, US, 22101
Last Update: 29/03/2026
We’re a unified force of 170,000+ Associates, taking action every day toward the world we want tomorrow. Our Five Principles have kept us true to ourselves and to our commitment to treat others in ways that are consistent with those values. Having stood the test of ti...
Compliance Ranges Comparison
Tulip Food Company
Mars
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for Tulip Food Company in 2026.
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for Mars in 2026.
Incident History - Tulip Food Company (X = Date, Y = Severity)
Tulip Food Company cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mars (X = Date, Y = Severity)
Mars cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Tulip Food Company
Mars
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: *.*.