Comparison Overview
Leidos Australia
Leidos Australia
N/A
Last Update: 26/03/2026
Leidos is a Fortune 500® technology, engineering, and science solutions and services leader working to solve the world's toughest challenges in the defence, intelligence, civil, and health markets. Headquartered in Virginia, it currently has 45,000+ employees and report...
L3 Technologies
600 Third Ave, New York, 10016, US
Last Update: 30/03/2026
With headquarters in New York City and approximately 31,000 employees worldwide, L3 develops advanced defense technologies and commercial solutions in pilot training, aviation security, night vision and EO/IR, weapons, maritime systems and space. The company reported 20...
Compliance Ranges Comparison
Leidos Australia
L3 Technologies
Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for Leidos Australia in 2026.
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for L3 Technologies in 2026.
Incident History - Leidos Australia (X = Date, Y = Severity)
Leidos Australia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - L3 Technologies (X = Date, Y = Severity)
L3 Technologies cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Leidos Australia
L3 Technologies
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.