Comparison Overview
Hoogenboom
Hoogenboom
Driemansteeweg 694, Rotterdam, 3084 CD, NL
Last Update: 07/01/2026
Hoogenboom is totaal leverancier van mobiliteit in Groot Rotterdam, Vlaardingen, de Zuid-Hollandse Eilanden en omgeving. De ongeveer 300 medewerkers die werkzaam zijn voor één van de bedrijfsonderdelen van Hoogenboom, zetten zich dagelijks in om onze klanten optimaal mo...
Ford Motor Company
1 American Rd, Dearborn, Michigan, US, 48126
Last Update: 26/06/2026
We don't just make history -- we make the future. Ford put the world on wheels over a century ago, and our teams are re-inventing icons and creating groundbreaking connected and electric vehicles for the next century. We believe in serving our customers, our communities...
Compliance Ranges Comparison
Hoogenboom
Ford Motor Company
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Hoogenboom in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Ford Motor Company in 2026.
Incident History - Hoogenboom (X = Date, Y = Severity)
Hoogenboom cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Ford Motor Company (X = Date, Y = Severity)
Ford Motor Company cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Hoogenboom
Ford 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: *.*.