Comparison Overview
Autocentro Baistrocchi
Autocentro Baistrocchi
Via San Leonardo 146/A, Parma, 43122, IT
Last Update: 05/01/2026
Autocentro Baistrocchi è Concessionario Audi, Audi Sport, Audi Prima Scelta :plus, Das WeltAuto, Porsche, CUPRA, SEAT, ŠKODA, Volkswagen, Volkswagen Veicoli Commerciali per Parma e provincia dal 1950. Dobbiamo le nostre origini a Egisto Baistrocchi, già noto per la sua...
PACCAR
777 106th Ave NE, Bellevue, 98004, US
Last Update: 12/09/2026
PACCAR is a global technology leader in the design, manufacture and customer support of premium light-, medium- and heavy-duty trucks under the Kenworth, Peterbilt and DAF nameplates. PACCAR also designs and manufactures advanced diesel engines, provides financial servi...
Compliance Ranges Comparison
Autocentro Baistrocchi
PACCAR
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Autocentro Baistrocchi in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for PACCAR in 2026.
Incident History - Autocentro Baistrocchi (X = Date, Y = Severity)
Autocentro Baistrocchi cyber incidents detection timeline including parent company and subsidiaries.
Incident History - PACCAR (X = Date, Y = Severity)
PACCAR cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Autocentro Baistrocchi
PACCAR
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.