Comparison Overview
DHL Express Latvia

DHL Express Latvia
Mazā Gramzdas iela 9A, Lidosta “Rīga”,, Marupe, Mārupe 1053, LV
Last Update: 22/04/2026
DHL Group is the world’s leading logistic company. The Group connects people and markets and is an enabler of global trade. It aspires to be the first choice for customers, employees and investors worldwide. To this end, DHL Group is focusing on growth in its profitable...

Brink’s Inc
1801 Bayberry Ct, Richmond, 23226, US
Last Update: 13/09/2026
The Brink’s Company (NYSE:BCO) is a leading global provider of cash and valuables management, digital retail solutions (DRS), and ATM managed services (AMS). Our customers include financial institutions, retailers, government agencies, mints, jewelers and other commerci...
Compliance Ranges Comparison

DHL Express Latvia







Brink’s Inc






Benchmark & Cyber Underwriting Signals
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for DHL Express Latvia in 2026.
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
Brink’s Inc has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - DHL Express Latvia (X = Date, Y = Severity)
DHL Express Latvia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Brink’s Inc (X = Date, Y = Severity)
Brink’s Inc cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

DHL Express Latvia

Brink’s Inc
FAQ
Latest Global CVEs
A vulnerability was determined in xuxueli xxl-job up to 3.5.0. The impacted element is an unknown function of the file /jobgroup/insert. This manipulation of the argument Name causes cross site scripting. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.
A vulnerability was found in Moore Threads MTT S80 Driver Package 340.150. The affected element is the function sub_140006F0C in the library mtdispkm64.sys of the component IOCTL Handler. The manipulation results in improper privilege management. Attacking locally is a requirement. The vendor was contacted early about this disclosure but did not respond in any way.
vLLM Mooncake connector through 0.29.0 fails to properly manage GPU KV cache block ownership when concurrent child requests share a single transfer ID in prefill/decode disaggregated deployments. Attackers can trigger GPU memory exhaustion by submitting completion requests with multiple prompts, causing orphaned KV cache blocks to accumulate until process restart and eventually preventing legitimate requests from executing.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/mooncake/mooncake_connector.py#L1978-L1989
- https://github.com/vllm-project/vllm/pull/49796
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-gpu-kv-cache-leak-via-mooncake-transfer-id-collision
vLLM through 0.29.0 fails to validate the tp_size parameter in kv_transfer_params on OpenAI-compatible completion endpoints, allowing attackers to allocate unbounded memory. Attackers can supply arbitrary tp_size values in prefill/decode disaggregated deployments to exhaust memory and trigger kernel OOM-kill of the decode worker process.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/utils.py#L569-L573
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/metadata.py#L277
- https://github.com/vllm-project/vllm/pull/51137
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-unvalidated-nixl-tp-size
vLLM through 0.29.0 contains a resource exhaustion vulnerability in MooncakeConnector where rejected prefill requests create ownerless transfer placeholders that are never reclaimed. Attackers can send rejected requests to exhaust sender task pools, causing valid requests to be delayed by up to 480 seconds while health checks continue returning success.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/mooncake/mooncake_connector.py#L1234-L1242
- https://github.com/vllm-project/vllm/pull/51236
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-resource-exhaustion-via-ownerless-mooncake-transfer-placeholders