Comparison Overview
Marina Militare Italiana
Marina Militare Italiana
Piazza della Marina, 4, Roma, Lazio, IT, 00196
Last Update: 10/03/2026
Alla Marina Militare è affidato il controllo e la condotta delle operazioni navali nelle acque territoriali ed internazionali, per assicurare la difesa degli interessi vitali del Paese contro ogni possibile minaccia al nostro territorio, ai concittadini all’estero, alle...
British Army
Trenchard Lines, Andover, Hampshire, GB
Last Update: 18/09/2026
Joining the British Army, you’ll get much more from life than you ever would with a civilian career – you’ll have the opportunity to do something that really matters, with a team that are like family to you. The sense of belonging in the Army is next level: when you’ve ...
Compliance Ranges Comparison
Marina Militare Italiana
British Army
Benchmark & Cyber Underwriting Signals
Incidents vs Armed Forces Industry Avg (This Year)
No incidents recorded for Marina Militare Italiana in 2026.
Incidents vs Armed Forces Industry Avg (This Year)
No incidents recorded for British Army in 2026.
Incident History - Marina Militare Italiana (X = Date, Y = Severity)
Marina Militare Italiana cyber incidents detection timeline including parent company and subsidiaries.
Incident History - British Army (X = Date, Y = Severity)
British Army cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Marina Militare Italiana
British Army
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.