Comparison Overview
AVIATAR
AVIATAR
Weg beim Jaeger 193, Hamburg, 22335, DE
Last Update: 12/03/2026
AVIATAR is part of the Digital Tech Ops Ecosystem developed by Lufthansa Technik. Our platform offers its users digital products ranging from predictive maintenance to automated fulfilment solutions. AVIATAR combines fleet management solutions, data science and enginee...
Textron
40 Westminster, Providence, RI, US, 02903
Last Update: 14/09/2026
Textron Inc. is a multi-industry company that leverages its global network of aircraft, defense, industrial and finance businesses to provide customers with innovative solutions and services. Textron is known around the world for its powerful brands such as Bell, Cessna...
Compliance Ranges Comparison
AVIATAR
Textron
Benchmark & Cyber Underwriting Signals
Incidents vs Aviation and Aerospace Component Manufacturing Industry Avg (This Year)
No incidents recorded for AVIATAR in 2026.
Incidents vs Aviation and Aerospace Component Manufacturing Industry Avg (This Year)
No incidents recorded for Textron in 2026.
Incident History - AVIATAR (X = Date, Y = Severity)
AVIATAR cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Textron (X = Date, Y = Severity)
Textron cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
AVIATAR
Textron
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.