Comparison Overview
Worldwide Logistics Group Germany
Worldwide Logistics Group Germany
Fabrikstraße 18, Owen, 73277, DE
Last Update: 28/03/2026
Logistics
UPS
55 Glenlake Parkway, NE, Atlanta, 30328, US
Last Update: 07/10/2026
Operating in more than 200 countries and territories, we’re committed to moving our world forward by delivering what matters. Beginning as a small messenger service, UPS was started by two enterprising teenagers and a $100 loan. Now, we’re almost 500,000 UPSers strong, ...
Compliance Ranges Comparison
Worldwide Logistics Group Germany
UPS
Benchmark & Cyber Underwriting Signals
Incidents vs Truck Transportation Industry Avg (This Year)
No incidents recorded for Worldwide Logistics Group Germany in 2026.
Incidents vs Truck Transportation Industry Avg (This Year)
UPS has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Worldwide Logistics Group Germany (X = Date, Y = Severity)
Worldwide Logistics Group Germany cyber incidents detection timeline including parent company and subsidiaries.
Incident History - UPS (X = Date, Y = Severity)
UPS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Worldwide Logistics Group Germany
UPS
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.