Comparison Overview
Lamborghini Lisboa
Lamborghini Lisboa
Rua São Francisco, , Lisboa, 2645-019, PT
Last Update: 03/02/2026
Obrigado por visitar a página de Linkedin da Lamborghini Lisboa, o único Concessionário autorizado Lamborghini em Portugal. Temos para lhe oferecer uma vasta selecção de viaturas novas bem como assistência Após-Venda, peças e merchandise. Em 1963 Ferrucio Lamborghini ...
Volvo Trucks
Herkulesgatan 75, Gothenburg, 405 08, SE
Last Update: 12/09/2026
Volvo Trucks supplies complete transport solutions for discerning professional customers with its full range of medium- and heavy-duty trucks. Customer support is provided via a global network of dealers with 2,200 service points in about 130 countries. Volvo trucks are...
Compliance Ranges Comparison
Lamborghini Lisboa
Volvo Trucks
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Lamborghini Lisboa in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Volvo Trucks in 2026.
Incident History - Lamborghini Lisboa (X = Date, Y = Severity)
Lamborghini Lisboa cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Volvo Trucks (X = Date, Y = Severity)
Volvo Trucks cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Lamborghini Lisboa
Volvo Trucks
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.