Comparison Overview
United States Space Force
United States Space Force
2020 United States Space Force Pentagon, Washington, 20360, US
Last Update: 01/06/2026
The U.S. Space Force (USSF) is a new branch of the Armed Forces, established on December 20, 2019 with enactment of the Fiscal Year 2020 National Defense Authorization Act. The USSF was established within the Department of the Air Force, meaning the Secretary of the Air...
Thales
6, Rue de la Verrerie, Meudon, 92190, FR
Last Update: 12/09/2026
Thales (Euronext Paris: HO) is a global leader in advanced technologies for the Defence, Aerospace, and Cyber & Digital sectors. Its portfolio of innovative products and services addresses several major challenges: sovereignty, security, sustainability and inclusion. T...
Compliance Ranges Comparison
United States Space Force
Thales
Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
United States Space Force has 55.16% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
Thales has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - United States Space Force (X = Date, Y = Severity)
United States Space Force cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Thales (X = Date, Y = Severity)
Thales cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
United States Space Force
Thales
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.