Comparison Overview
dsm-firmenich
dsm-firmenich
N/A
Last Update: 02/04/2026
We are dsm-firmenich – innovators in nutrition, health, and beauty. We bring progress to life by combining the essential, the desirable, and the sustainable. From our master perfumers and flavorists to our expert nutritionists and scientists, our trailblazing teams wo...
Bayer
Kaiser-Wilhelm-Allee, Leverkusen, North Rhine-Westphalia, DE, 51373
Last Update: 05/07/2026
Bayer is a global enterprise with core competencies in the life science fields of healthcare and nutrition. We design our products and services to serve the most essential human needs of health and nutrition. At the same time, we strive to address some of the world’s bi...
Compliance Ranges Comparison
dsm-firmenich
Bayer
Benchmark & Cyber Underwriting Signals
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for dsm-firmenich in 2026.
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for Bayer in 2026.
Incident History - dsm-firmenich (X = Date, Y = Severity)
dsm-firmenich cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bayer (X = Date, Y = Severity)
Bayer cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
dsm-firmenich
Bayer
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: *.*.