Comparison Overview
DHL Global Event Logistics
DHL Global Event Logistics
Welserstrasse 10d, Köln, 51149, DE
Last Update: 28/04/2026
𝗗𝗛𝗟 𝗚𝗹𝗼𝗯𝗮𝗹 𝗘𝘃𝗲𝗻𝘁 𝗟𝗼𝗴𝗶𝘀𝘁𝗶𝗰𝘀 𝗶𝘀 𝘁𝗵𝗲 𝗹𝗲𝗮𝗱𝗶𝗻𝗴 𝗽𝗿𝗼𝘃𝗶𝗱𝗲𝗿 𝗳𝗼𝗿 𝗶𝗻𝘁𝗲𝗿𝗻𝗮𝘁𝗶𝗼𝗻𝗮𝗹 𝗲𝘅𝗵𝗶𝗯𝗶𝘁𝗶𝗼𝗻 𝗮𝗻𝗱 𝗲𝘃𝗲𝗻𝘁 𝗹𝗼𝗴𝗶𝘀𝘁𝗶𝗰 𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀. With multiple locations worldwide, DHL Global Event Logistics combi...
PostNord
Terminalvägen 24, Solna, SE, 17173
Last Update: 13/09/2026
Moving the Nordics forward. PostNord is a leading provider of parcel and logistics services to, from, and within the Nordic region. We ensure the provision of a postal service to households and businesses in Sweden, regardless of where they live and work. PostNord con...
Compliance Ranges Comparison
DHL Global Event Logistics
PostNord
Benchmark & Cyber Underwriting Signals
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for DHL Global Event Logistics in 2026.
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for PostNord in 2026.
Incident History - DHL Global Event Logistics (X = Date, Y = Severity)
DHL Global Event Logistics cyber incidents detection timeline including parent company and subsidiaries.
Incident History - PostNord (X = Date, Y = Severity)
PostNord cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
DHL Global Event Logistics
PostNord
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.