Comparison Overview
ID Logistics Chile
ID Logistics Chile
Santiago de Chile, 7550171, CL
Last Update: 07/12/2025
ID Logistics es un grupo internacional de Contract Logistcs, con ingresos de 3.3 millones de euros en 2024. ID Logistics tiene más de 450 centros en 19 países, que representan más de 9 millones de metros cuadrados de instalaciones de almacenamiento en Europa, América, A...
PostNL
Waldorpstraat 3, Den Haag, 2521 CA, NL
Last Update: 12/09/2026
Welcome! We are PostNL. Your favorite delivery service is what we want to be. Every day, over 35,000 colleagues work hard to achieve this goal, on your streets and in your neighborhood, in our sorting centers and depots, and at the office. On an average day, we deliver ...
Compliance Ranges Comparison
ID Logistics Chile
PostNL
Benchmark & Cyber Underwriting Signals
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for ID Logistics Chile in 2026.
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for PostNL in 2026.
Incident History - ID Logistics Chile (X = Date, Y = Severity)
ID Logistics Chile cyber incidents detection timeline including parent company and subsidiaries.
Incident History - PostNL (X = Date, Y = Severity)
PostNL cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
ID Logistics Chile
PostNL
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.