Comparison Overview
Eberspächer Group

Eberspächer Group
Eberspächerstrasse 24, Esslingen, 73730, DE
Last Update: 30/03/2026
The Eberspächer Group is one of the world's leading system developers and suppliers to the automotive industry. With its three Divisions - Exhaust Technology, Climate Control Systems, and Automotive Controls - the Company is a valued innovation partner and pacesetter fo...

TVS Motor Company
Hosur, Tamil Nadu , Hosur, 635109, IN
Last Update: 03/04/2026
TVS Motor Company is a reputed two and three-wheeler manufacturer globally, championing progress through Mobility with a focus on sustainability. Rooted in our 100-year legacy of Trust, Value, and Passion for Customers and Exactness, we take pride in making internationa...
Compliance Ranges Comparison

Eberspächer Group







TVS Motor Company






Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Eberspächer Group in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for TVS Motor Company in 2026.
Incident History - Eberspächer Group (X = Date, Y = Severity)
Eberspächer Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TVS Motor Company (X = Date, Y = Severity)
TVS Motor Company cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Eberspächer Group

TVS Motor Company
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: *.*.