Comparison Overview
Yamaha Motor Co., Ltd.
Yamaha Motor Co., Ltd.
2500, 磐田市新貝, 438-8501, JP
Last Update: 03/04/2026
Yamaha Motor is a world-leading enterprise known for its products for land mobility, such as motorcycles, all-terrain vehicles, and electrically power-assisted bicycles, marine products, such as boats and outboard motors, and industrial machinery and robots, such as sur...
Lear Corporation
21557 Telegraph Rd, Southfield , 48033, US
Last Update: 01/04/2026
Lear Corporation (NYSE: LEA) is a global automotive leader in Seating and E-Systems. The company designs, manufactures, and delivers advanced technologies to the world’s major automakers. Building on more than 100 years of heritage, Lear is the largest U.S.-based automo...
Compliance Ranges Comparison
Yamaha Motor Co., Ltd.
Lear Corporation
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
Yamaha Motor Co., Ltd. has 59.18% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Lear Corporation in 2026.
Incident History - Yamaha Motor Co., Ltd. (X = Date, Y = Severity)
Yamaha Motor Co., Ltd. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lear Corporation (X = Date, Y = Severity)
Lear Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Yamaha Motor Co., Ltd.
Lear Corporation
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: *.*.