Comparison Overview
SAF-HOLLAND CANADA
SAF-HOLLAND CANADA
595 Athlone Ave, Woodstock, N4V, CA
Last Update: 03/02/2026
SAF-HOLLAND S.A. with its headquarters in Luxembourg is the largest independent listed supplier to the commercial vehicle market in Europe and is present in most of the world's markets. The merger of two regional champions - SAF in Europe and Holland in the USA - in Dec...
Schneider
3101 S. Packerland Drive, Green Bay, WI, US, 54306-2545
Last Update: 01/04/2026
Put us on the job and consider it done. Schneider is a premier provider of transportation and logistics services headquartered in Green Bay, Wisconsin, and with offices in Chicago, Dallas and many cities in between. Offering one of the broadest portfolios in the industr...
Compliance Ranges Comparison
SAF-HOLLAND CANADA
Schneider
Benchmark & Cyber Underwriting Signals
Incidents vs Truck Transportation Industry Avg (This Year)
No incidents recorded for SAF-HOLLAND CANADA in 2026.
Incidents vs Truck Transportation Industry Avg (This Year)
No incidents recorded for Schneider in 2026.
Incident History - SAF-HOLLAND CANADA (X = Date, Y = Severity)
SAF-HOLLAND CANADA cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Schneider (X = Date, Y = Severity)
Schneider cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
SAF-HOLLAND CANADA
Schneider
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: *.*.