Comparison Overview
Solvay
Solvay
Rue de Ransbeek 310, Brussels, Belgium, BE, 1120
Last Update: 04/04/2026
For over 160 years, Solvay has been a pioneer in science and innovation, mastering the essential chemistry that powers progress across generations. We are more than a chemical company — we are a catalyst for sustainable transformation, delivering vital solutions that sh...
Evonik
Evonik Industries AG, Rellinghauser Straße 1-11, Essen, NRW, DE, 45128
Last Update: 05/04/2026
Evonik goes beyond the boundaries of chemistry with its combination of innovative strength and leading technological expertise. The global chemical company, headquartered in Essen, Germany, is active in more than 100 countries. The common motivation of the approximately...
Compliance Ranges Comparison
Solvay
Evonik
Benchmark & Cyber Underwriting Signals
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for Solvay in 2026.
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for Evonik in 2026.
Incident History - Solvay (X = Date, Y = Severity)
Solvay cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Evonik (X = Date, Y = Severity)
Evonik cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Solvay
Evonik
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: *.*.