Comparison Overview
APT
APT
undefined, Abu Dhabi, undefined, 136565, AE
Last Update: 21/02/2026
APT manufactures high-performance non-lethal and less-than-lethal pyrotechnics and low-velocity ammunition solutions for armed forces, security forces and law enforcement. With one of the world’s most advanced pyrotechnics manufacturing facilities, we produce high-quali...
NAVAL GROUP
40-42 rue du docteur FInlay, Paris cedex 15, 75732, FR
Last Update: 14/09/2026
As an international naval defence player, Naval Group is a partner for countries seeking to maintain control of their maritime sovereignty. Naval Group develops innovative solutions to meet its customers’ requirements. The group is present throughout the entire life cyc...
Compliance Ranges Comparison
APT
NAVAL GROUP
Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for APT in 2026.
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
NAVAL GROUP has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - APT (X = Date, Y = Severity)
APT cyber incidents detection timeline including parent company and subsidiaries.
Incident History - NAVAL GROUP (X = Date, Y = Severity)
NAVAL GROUP cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
APT
NAVAL GROUP
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.