Comparison Overview
General Atomics Aeronautical Systems

General Atomics Aeronautical Systems
14200 Kirkham Way, Poway, CA, US, 92064
Last Update: 25/02/2026
At General Atomics Aeronautical Systems, Inc. (GA-ASI), we invent and pioneer disruptive technologies for military, security, environmental and civil operations worldwide. As the world leader in unmanned aerial systems, we design and engineer advanced long endurance unm...

Textron
40 Westminster, Providence, 02903, US
Last Update: 20/05/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

General Atomics Aeronautical Systems







Textron






Benchmark & Cyber Underwriting Signals
Incidents vs Aviation and Aerospace Component Manufacturing Industry Avg (This Year)
No incidents recorded for General Atomics Aeronautical Systems in 2026.
Incidents vs Aviation and Aerospace Component Manufacturing Industry Avg (This Year)
No incidents recorded for Textron in 2026.
Incident History - General Atomics Aeronautical Systems (X = Date, Y = Severity)
General Atomics Aeronautical Systems 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

General Atomics Aeronautical Systems

Textron
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.