Comparison Overview
DHL Africa

DHL Africa
Cnr Fabriek & Van Acht Streets, Johannesburg, 1600, ZA
Last Update: 22/01/2026
From humble beginnings to global market leader founded in San Francisco more than 45 years ago by three budding entrepreneurs - Adrian Dalsey, Larry Hillblom and Robert Lynn - DHL has continued to expand at a phenomenal rate. Today, it stands tall as the global market l...

Aramex
Dubai Logistics City, Dubai, AE, 3841
Last Update: 13/09/2026
Founded in 1982, Aramex has emerged as a global leader in logistics and transportation, renowned for its innovative services tailored to businesses and consumers. As a listed company on the Dubai Financial Market (since 2005) and headquartered in the UAE, our strategic ...
Compliance Ranges Comparison

DHL Africa







Aramex






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

DHL Africa

Aramex
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.