Comparison Overview
Bnode
Bnode
Boulevard Anspach 1, Brussels, Brussels Region, BE, 1000
Last Update: 13/09/2026
Bnode is a parcel logistics group operating across Europe, North America and Asia-Pacific, built on three specialized business units. Paxon delivers 3PL and fulfilment services through Active Ants, Base Logistics, Staci and Radial. Landmark Global manages cross-border e...
ID Logistics Group
55, Chemin des Engranauds, Orgon, 13660, FR
Last Update: 14/09/2026
ID Logistics, headed by Eric Hémar, is an international contract logistics group with revenues of €3.3 billion in 2024. ID Logistics manages nearly 450 sites in 19 countries, representing more than 9 million m² operated in Europe, America, Asia and Africa, with 42,000 e...
Compliance Ranges Comparison
Bnode
ID Logistics Group
Benchmark & Cyber Underwriting Signals
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for Bnode in 2026.
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for ID Logistics Group in 2026.
Incident History - Bnode (X = Date, Y = Severity)
Bnode cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ID Logistics Group (X = Date, Y = Severity)
ID Logistics Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Bnode
ID Logistics Group
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.