Comparison Overview
ADASI

ADASI
Prestige Tower 17, 79th street, Abu Dhabi, AE
Last Update: 10/03/2026
Headquartered in the UAE, ADASI is a reliable end-to-end solution provider within the autonomous systems industry, with a stronghold in the MENA region. Focused on the further development and evolution of our core activities, we constantly strive to develop and strengt...

V2X Inc
7901 Jones Branch Dr, Suite 700, McLean, Virginia, US, 22102
Last Update: 15/09/2026
V2X is a leading provider of critical mission solutions and support to defense clients globally, formed by the 2022 Merger of Vectrus and Vertex to build on more than 120 combined years of successful mission support. We deliver a comprehensive suite of integrated soluti...
Compliance Ranges Comparison

ADASI







V2X Inc






Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for ADASI in 2026.
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for V2X Inc in 2026.
Incident History - ADASI (X = Date, Y = Severity)
ADASI cyber incidents detection timeline including parent company and subsidiaries.
Incident History - V2X Inc (X = Date, Y = Severity)
V2X Inc cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

ADASI

V2X Inc
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.