Comparison Overview
vAuto by Cox Automotive
vAuto by Cox Automotive
6205 a Peachtree Dunwoody Rd NE, Atlanta, 30328, US
Last Update: 01/04/2026
A Cox Automotive brand since 2010, vAuto provides an industry-leading suite of inventory management solutions to help automotive dealers run their businesses better. Our solutions combine superior retail/wholesale market data and data science-driven insights to enable s...
Meituan
Wangjing International R&D Park, No.6 Wangjing East Road, Chaoyang District, Beijing, CN, 100102
Last Update: 12/09/2026
Adhering to the ‘Retail + Technology’ strategy, Meituan commits to its mission that 'We help people eat better, live better'. Since its establishment in March 2010, Meituan has advanced the digital upgrading of services and goods retail on both supply and demand sides....
Compliance Ranges Comparison
vAuto by Cox Automotive
Meituan
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for vAuto by Cox Automotive in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Meituan in 2026.
Incident History - vAuto by Cox Automotive (X = Date, Y = Severity)
vAuto by Cox Automotive cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Meituan (X = Date, Y = Severity)
Meituan cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
vAuto by Cox Automotive
Meituan
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.