Comparison Overview
VGRF Business Solutions
VGRF Business Solutions
165, Avenue du Bois de la Pie, Roissy-en-France, 95700, FR
Last Update: 22/04/2026
VGRF Business Solution est le pôle BtoB de Volkswagen Group Retail France. Il met à disposition des véhicules et des solutions sur mesure pour les professionnels. Grâce à une unité spécialisée dédiée pour toute la France, nous distribuons plus de 18 000 véhicules auprè...
AutoNation
200 SW 1st Avenue, Ft. Lauderdale, 33301, US
Last Update: 01/04/2026
As America’s most admired automotive retailer, AutoNation is transforming the automotive industry through its bold leadership, innovation, and comprehensive brand extensions. We are committed to hiring driven, diverse Associates and supporting them in growing their car...
Compliance Ranges Comparison
VGRF Business Solutions
AutoNation
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Motor Vehicles Industry Avg (This Year)
No incidents recorded for VGRF Business Solutions in 2026.
Incidents vs Retail Motor Vehicles Industry Avg (This Year)
No incidents recorded for AutoNation in 2026.
Incident History - VGRF Business Solutions (X = Date, Y = Severity)
VGRF Business Solutions cyber incidents detection timeline including parent company and subsidiaries.
Incident History - AutoNation (X = Date, Y = Severity)
AutoNation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
VGRF Business Solutions
AutoNation
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.