Comparison Overview
DHL Express
DHL Express
Fritz-Erler-Strasse 5, Bonn, 53113, DE
Last Update: 01/04/2026
Leading the way in international logistics across an unparalleled network of 220 countries and territories. With decades of experience, we’re your ideal partner for flexible, sustainable shipping to support your growing business and help you expand into new markets. DH...
A.P. Moller - Maersk
Esplanaden 50, Copenhagen, DK, 1098
Last Update: 14/09/2026
A.P. Moller - Maersk is an integrated transport and logistics company; going all the way, together, for our customers and society. ALL THE WAY is our commitment to connect the world so that everyone has both the possibility and the ability to trade, grow and thrive. The...
Compliance Ranges Comparison
DHL Express
A.P. Moller - Maersk
Benchmark & Cyber Underwriting Signals
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for DHL Express in 2026.
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for A.P. Moller - Maersk in 2026.
Incident History - DHL Express (X = Date, Y = Severity)
DHL Express cyber incidents detection timeline including parent company and subsidiaries.
Incident History - A.P. Moller - Maersk (X = Date, Y = Severity)
A.P. Moller - Maersk cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
DHL Express
A.P. Moller - Maersk
FAQ
Latest Global CVEs
vLLM through 0.29.0 fails to properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/push_worker.py#L162-L181
- https://github.com/vllm-project/vllm/pull/55677
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-rejected-requests
redis-parser through 3.0.0 contains a denial of service vulnerability in the RESP protocol parser that allows malicious Redis endpoints to crash the client process through unbounded recursion on nested arrays. Attackers can send crafted RESP byte streams with repeated array headers that exhaust the V8 call stack, causing an uncaught RangeError that terminates the Node.js process without triggering error handling callbacks.
- https://github.com/NodeRedis/node-redis-parser
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L204-L213
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L291-L306
- https://github.com/redis/ioredis/issues/2108
- https://www.vulncheck.com/advisories/redis-parser-through-3.0.0-denial-of-service-via-unbounded-recursion
Improper neutralization of special elements in output used by a downstream component ('injection') in Azure Cosmos DB allows an authorized attacker to elevate privileges over a network.
Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.