Comparison Overview
Scania Logistics

Scania Logistics
Blaloweg 22, Zwolle, 8041 AH, NL
Last Update: 27/03/2026
Scania Logistics is responsible for leading logistics flows all over the world. With multiple logistic hubs in the Netherlands (Hasselt and Zwolle) and logistic centres in Sweden and Brazil we control our supply chain in a sustainable, flexible and profitable way.

C.H. Robinson
14701 Charlson Road, Eden Prairie, 55347, US
Last Update: 02/04/2026
C.H. Robinson is the global leader in Lean AI supply chains. For more than a century, companies everywhere have looked to us to reimagine how goods move. Now, as we redefine what’s next for the industry, that same drive fuels our commitment to Building Tomorrow’s Supply...
Compliance Ranges Comparison

Scania Logistics







C.H. Robinson






Benchmark & Cyber Underwriting Signals
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for Scania Logistics in 2026.
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for C.H. Robinson in 2026.
Incident History - Scania Logistics (X = Date, Y = Severity)
Scania Logistics cyber incidents detection timeline including parent company and subsidiaries.
Incident History - C.H. Robinson (X = Date, Y = Severity)
C.H. Robinson cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Scania Logistics

C.H. Robinson
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.