Comparison Overview
VanderLinden
VanderLinden
Eisenhowerweg 39, Veghel, 5466 AB, NL
Last Update: 21/04/2026
Bij VanderLinden geloven wij dat gebouwen zich moeten aanpassen aan de mensen die zich erin begeven. Daarom optimaliseren wij gebouwen en terreinen zodat ze slim, duurzaam, comfortabel en veilig zijn. Dit doen we middels advies, ontwerp, realisatie, onderhoud, beheer en...
United Rentals
100 First Stamford Place, Suite 700, Stamford, CT, US, 06902
Last Update: 13/09/2026
As North America’s largest equipment rental company, with 1600+ stores across North America, Europe, Australia and New Zealand, we serve construction and industrial companies, utilities, municipalities, homeowners, and communities, with the goal of fulfilling customer n...
Compliance Ranges Comparison
VanderLinden
United Rentals
Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for VanderLinden in 2026.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for United Rentals in 2026.
Incident History - VanderLinden (X = Date, Y = Severity)
VanderLinden cyber incidents detection timeline including parent company and subsidiaries.
Incident History - United Rentals (X = Date, Y = Severity)
United Rentals cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
VanderLinden
United Rentals
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.