Comparison Overview
Federal Aviation Administration

Federal Aviation Administration
800 Independence Ave., SW, Washington, 20591, US
Last Update: 10/09/2026
The FAA is on the leading edge of a new frontier in commercial space transportation, building the next generation (NextGen) of satellite-based navigation systems, and fostering the safe integration of unmanned aerial systems into our airspace. We can only dream of what ...

Embraer
Av. Brigadeiro Faria Lima, 2170, São José dos Campos, 12227-901, BR
Last Update: 13/09/2026
A global aerospace company headquartered in Brazil, Embraer has businesses in Commercial and Executive Aviation, Defense & Security, and Agricultural Aviation. The company designs, develops, manufactures and markets aircraft and systems, providing Services and Support t...
Compliance Ranges Comparison

Federal Aviation Administration







Embraer






Benchmark & Cyber Underwriting Signals
Incidents vs Aviation and Aerospace Component Manufacturing Industry Avg (This Year)
No incidents recorded for Federal Aviation Administration in 2026.
Incidents vs Aviation and Aerospace Component Manufacturing Industry Avg (This Year)
No incidents recorded for Embraer in 2026.
Incident History - Federal Aviation Administration (X = Date, Y = Severity)
Federal Aviation Administration cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Embraer (X = Date, Y = Severity)
Embraer cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Federal Aviation Administration

Embraer
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.