Comparison Overview
World Courier
World Courier
10 Fetter Lane, London, EC4A 2EJ, GB
Last Update: 04/04/2026
World Courier, a part of Cencora (formerly AmerisourceBergen), provides specialty logistics services to drive the clinical and commercial success of our partners around the globe. We deliver peace of mind through world-class supply chain programs, transport services, de...
Lineage
46500 Humboldt Dr., Novi, MI, US, 48377
Last Update: 02/04/2026
Lineage is one of the world’s leading temperature-controlled industrial REITs and integrated solutions providers with a global network of over 480 strategically located facilities, totaling nearly 2.9 billion cubic feet of capacity across countries in North America, Eur...
Compliance Ranges Comparison
World Courier
Lineage
Benchmark & Cyber Underwriting Signals
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for World Courier in 2026.
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for Lineage in 2026.
Incident History - World Courier (X = Date, Y = Severity)
World Courier cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lineage (X = Date, Y = Severity)
Lineage cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
World Courier
Lineage
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: *.*.