Comparison Overview
Groupe PSA
Groupe PSA
Route de Gisy, Vélizy-Villacoublay, 78140, FR
Last Update: 06/03/2026
Groupe PSA is now Stellantis, one of the world's leading automakers and a mobility provider. Follow us here: https://www.linkedin.com/company/stellantis/
Mercedes-Benz AG
Am Wallgraben, Stuttgart, Baden-Württemberg, DE, 70563
Last Update: 06/07/2026
"Love of invention will never end." - Carl Benz Learn more about us as we continue to pioneer the future of driving excellence. Data privacy: mb4.me/provider_privacy Mercedes-Benz AG Mercedesstraße 120 70372 Stuttgart Germany Phone: +49 7 11 17-0 E-Mail: dialog@mer...
Compliance Ranges Comparison
Groupe PSA
Mercedes-Benz AG
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Groupe PSA in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Mercedes-Benz AG in 2026.
Incident History - Groupe PSA (X = Date, Y = Severity)
Groupe PSA cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mercedes-Benz AG (X = Date, Y = Severity)
Mercedes-Benz AG cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Groupe PSA
Mercedes-Benz AG
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: *.*.