Comparison Overview
Ford Pro
Ford Pro
16800 Executive Plaza Dr, Dearborn, 48126, US
Last Update: 29/03/2026
Ford Pro™ is Ford Motor Company’s commercial vehicle division, offering a one-stop shop of work-ready vehicles, software, service, charging, and financing solutions that can help make running a fleet simpler and more productive. Our focus is on enabling businesses and ...
PT Astra Honda Motor
Jl. Laksda Yos Sudarso, Jakarta Utara, 14350, ID
Last Update: 01/04/2026
PT Astra Honda Motor (AHM) is a manufacturing company which produces motorcyle of Honda brand. A collaboration of strong Astra Management System and Honda high technology makes AHM the leading company in motorcycle market in indonesia. Now PT. Astra Honda Motor becomin...
Compliance Ranges Comparison
Ford Pro
PT Astra Honda Motor
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Ford Pro in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for PT Astra Honda Motor in 2026.
Incident History - Ford Pro (X = Date, Y = Severity)
Ford Pro cyber incidents detection timeline including parent company and subsidiaries.
Incident History - PT Astra Honda Motor (X = Date, Y = Severity)
PT Astra Honda Motor cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Ford Pro
PT Astra Honda Motor
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: *.*.