Comparison Overview
Turkish Aerospace

Turkish Aerospace
Fethiye Mahallesi, Havacilik Bulvari No:17, Ankara, 06980, TR
Last Update: 07/08/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...

Safran
2, Boulevard du général Martial Valin, Paris, 75015, FR
Last Update: 02/04/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

Turkish Aerospace







Safran






Benchmark & Cyber Underwriting Signals
Incidents vs Aviation and Aerospace Component Manufacturing Industry Avg (This Year)
Turkish Aerospace has 33.33% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Aviation and Aerospace Component Manufacturing Industry Avg (This Year)
No incidents recorded for Safran in 2026.
Incident History - Turkish Aerospace (X = Date, Y = Severity)
Turkish Aerospace 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

Turkish Aerospace

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