Comparison Overview
Yazaki Portugal
Yazaki Portugal
PT
Last Update: 04/04/2026
YAZAKI’s timeline of success dates back to 1929 when Sadami YAZAKI began selling wiring harnesses for automobiles. As a truly global company deeply rooted in Japanese cultural traditions and values, YAZAKI strives to be a reliable partner to its customers as well as...
Volvo Group
Gropegårdsgatan 2, Göteborg, SE, 417 15
Last Update: 01/04/2026
The Volvo Group is one of the world’s leading manufacturers of trucks, buses, construction equipment and marine and industrial engines. The Group also provides complete solutions for financing and service. The Volvo Group, with its headquarters in Gothenburg, employs ab...
Compliance Ranges Comparison
Yazaki Portugal
Volvo Group
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Yazaki Portugal in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
Volvo Group has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Yazaki Portugal (X = Date, Y = Severity)
Yazaki Portugal cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Volvo Group (X = Date, Y = Severity)
Volvo Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Yazaki Portugal
Volvo 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: *.*.