Comparison Overview
DHL Sri Lanka
DHL Sri Lanka
No. 148, Vauxhall Street, Colombo 02, Colombo 02, 00200, LK
Last Update: 28/03/2026
DHL is the global market leader in the logistics industry and "The Logistics company for the world”. With more than 325,000 employees in over 220 countries and territories worldwide, DHL connects people and businesses securely and reliably, enabling global trade flows. ...
DHL
Charles-de-Gaulle-Str. 20, Bonn, DE, 53113
Last Update: 13/09/2026
DHL is the leading global brand in the logistics industry. Our divisions offer an unrivaled portfolio of logistics services ranging from national and international parcel delivery, e-commerce shipping and fulfillment solutions, international express, road, air and ocean...
Compliance Ranges Comparison
DHL Sri Lanka
DHL
Benchmark & Cyber Underwriting Signals
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for DHL Sri Lanka in 2026.
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
DHL has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - DHL Sri Lanka (X = Date, Y = Severity)
DHL Sri Lanka cyber incidents detection timeline including parent company and subsidiaries.
Incident History - DHL (X = Date, Y = Severity)
DHL cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
DHL Sri Lanka
DHL
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.