Comparison Overview
Tenneco
Tenneco
15701 Technology Dr., Northville, Michigan, US, 48168
Last Update: 02/04/2026
We’re united by one purpose: to be the most trusted partner and the best manufacturer and distributor to the transportation industry. And we’re doing it by leaning into the one thing no one can copy: our culture — our sustainable competitive advantage. The Tenneco Way ...
Iveco Group
Via Puglia 35, Torino, 10156, IT
Last Update: 01/04/2026
Iveco Group N.V. (MI: IVG) is the home of unique people and brands that power your business and mission to advance a more sustainable society. The seven brands are each a major force in its specific business: IVECO, a pioneering commercial vehicles brand that designs, m...
Compliance Ranges Comparison
Tenneco
Iveco Group
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Tenneco in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Iveco Group in 2026.
Incident History - Tenneco (X = Date, Y = Severity)
Tenneco cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Iveco Group (X = Date, Y = Severity)
Iveco Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Tenneco
Iveco 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: *.*.