Comparison Overview
Marquardt Group
Marquardt Group
Schloss-Straße 16, Rietheim-Weilheim, 78604, DE
Last Update: 02/04/2026
Founded in 1925 and headquartered in Rietheim-Weilheim, Germany, the family-owned company Marquardt is one of the world's leading manufacturers of mechatronic switching and operating systems. The mechatronics specialist's products - including operating components, vehic...
ZF Group
Löwentaler Straße 20, Friedrichshafen, 88046, DE
Last Update: 04/04/2026
ZF is a global technology company supplying advanced mobility products and systems for passenger cars, commercial vehicles and industrial technology. Its comprehensive product range is primarily aimed at vehicle manufacturers, mobility providers and start-up companies i...
Compliance Ranges Comparison
Marquardt Group
ZF Group
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Parts Manufacturing Industry Avg (This Year)
No incidents recorded for Marquardt Group in 2026.
Incidents vs Motor Vehicle Parts Manufacturing Industry Avg (This Year)
No incidents recorded for ZF Group in 2026.
Incident History - Marquardt Group (X = Date, Y = Severity)
Marquardt Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ZF Group (X = Date, Y = Severity)
ZF Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Marquardt Group
ZF Group
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: *.*.