Comparison Overview
ID Logistics US
ID Logistics US
P.O. Box 931, None, Scranton, PA, US, 18501
Last Update: 08/02/2026
ABOUT ID LOGISTICS: ID Logistics is an international contract logistics group, with revenue of € 3.3 B in 2024. ID Logistics has more than 450 sites across 18 countries, representing more than 9 million square meters of warehousing facilities in Europe, America, Asia an...
Penske Truck Leasing
2675 Morgantown Rd, Reading, 19607, US
Last Update: 02/04/2026
Penske Truck Leasing is a Penske Transportation Solutions company headquartered in Reading, Pennsylvania. A leading provider of innovative transportation solutions, Penske operates and maintains nearly 400,000 vehicles and serves its customers from approximately 1,000 m...
Compliance Ranges Comparison
ID Logistics US
Penske Truck Leasing
Benchmark & Cyber Underwriting Signals
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for ID Logistics US in 2026.
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for Penske Truck Leasing in 2026.
Incident History - ID Logistics US (X = Date, Y = Severity)
ID Logistics US cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Penske Truck Leasing (X = Date, Y = Severity)
Penske Truck Leasing cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
ID Logistics US
Penske Truck Leasing
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: *.*.