Comparison Overview
General Atomics AeroTec Systems

General Atomics AeroTec Systems
Galileostraße 396, Gauting, 82131, DE
Last Update: 16/02/2026
General Atomics AeroTec Systems GmbH (GA-ATS) is the result of the acquisition of RUAG Aerospace Services GmbH and focuses on the maintenance and repair of business jets and military helicopters as well as the production and maintenance of the Dornier 228 at the Oberpfa...

Safran
2, Boulevard du général Martial Valin, Paris, 75015, FR
Last Update: 12/09/2026
Safran is an international high-technology group, operating in the aviation (propulsion, equipment and interiors), defense and space markets. Its core purpose is to contribute to a safer, more sustainable world, where air transport is more environmentally friendly, comf...
Compliance Ranges Comparison

General Atomics AeroTec Systems







Safran






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

General Atomics AeroTec Systems

Safran
FAQ
Latest Global CVEs
Heym from 0.0.55 before 0.0.121 contains a privilege escalation vulnerability that allows shared collaborators to overwrite a workflow's error_workflow_id because the field is missing from OWNER_ONLY_EXECUTION_FIELDS. Attackers can point the error workflow to their own workflow with an HTTP node, and when the parent workflow errors the owner's decrypted credentials are injected and exfiltrated.
Nodemailer from 3.0.0 before 10.0.10 contains a quadratic complexity denial of service vulnerability in the SMTP client reply parser in SMTPConnection._onData and isPartialResponse. A malicious SMTP server or on-path attacker can stream continuation lines without a completion line before authentication, blocking the Node.js event loop and exhausting memory.
Nodemailer from 3.0.0 before 10.0.10 contains a denial of service vulnerability in MessageParser.parseHeaders that allows users to exhaust CPU through quadratic header unfolding. Attackers can supply large recipient lists or long headers that fold into tens of thousands of continuation lines, blocking the Node.js event loop during DKIM signing.
Nodemailer from 3.0.0 before 10.0.13 contains an improper input validation vulnerability in its address parser that fails to strip RFC 5322 comments inside angle-bracket addresses. Attackers can supply recipients like a display name with a parenthesized comment in the domain, so illegal characters reach envelope.to and RCPT TO, causing rejected delivery or parser interpretation conflicts that bypass domain allow-lists.
Nodemailer 3.0.0 before 10.0.13 has a regular expression denial of service in SMTPConnection._actionEHLO, whose four AUTH mechanism detection regexes contain overlapping whitespace sub-patterns that backtrack quadratically. A malicious or man-in-the-middle SMTP server can reply to EHLO with 250-AUTH, a long whitespace run and a non-matching token, blocking the Node.js event loop for tens of seconds to hours before authentication.