Comparison Overview
ACSS

ACSS
19810 N. 7th Avenue, Phoenix, 85027, US
Last Update: 15/12/2025
Aviation Communication & Surveillance Systems (ACSS) is a joint venture, with 70% owned by Acron Aviation and 30% owned by Thales. ACSS designs and manufactures products for all aircraft and helicopter segments, and supports products for air transport and regional airli...

Turkish Aerospace
Fethiye Mahallesi, Havacilik Bulvari No:17, Ankara, 06980, TR
Last Update: 13/09/2026
Türk Uçak Sanayii Anonim Ortaklığı (TUSAŞ), 28 Haziran 1973 tarihinde Türkiye'nin savunma sanayiinde dışa bağımlılığını azaltmak amacıyla Sanayi ve Teknoloji Bakanlığı bünyesinde kurulmuştur. Türk Hava Kuvvetleri'nin savaş uçağı ihtiyacının karşılanmasına yönelik olara...
Compliance Ranges Comparison

ACSS







Turkish Aerospace






Benchmark & Cyber Underwriting Signals
Incidents vs Aviation and Aerospace Component Manufacturing Industry Avg (This Year)
No incidents recorded for ACSS in 2026.
Incidents vs Aviation and Aerospace Component Manufacturing Industry Avg (This Year)
Turkish Aerospace has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - ACSS (X = Date, Y = Severity)
ACSS cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Turkish Aerospace (X = Date, Y = Severity)
Turkish Aerospace cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

ACSS

Turkish Aerospace
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.