Comparison Overview
AerCap

AerCap
AerCap House, Dublin, undefined, D02 YX20, IE
Last Update: 31/03/2026
AerCap is the global leader in aviation leasing with one of the most attractive order books in the industry. AerCap serves approximately 300 customers around the world with comprehensive fleet solutions. AerCap is listed on the New York Stock Exchange (AER) and is based...

Turkish Airlines
-, Istanbul, 34149, TR
Last Update: 10/07/2026
Turkish Airlines has soared to new heights since its first flight in 1933, becoming the airline that connects more countries than any other. Our commitment to excellence is reflected in the world-class service, comfort, and innovative travel experience we offer, designe...
Compliance Ranges Comparison

AerCap







Turkish Airlines






Benchmark & Cyber Underwriting Signals
Incidents vs Airlines and Aviation Industry Avg (This Year)
No incidents recorded for AerCap in 2026.
Incidents vs Airlines and Aviation Industry Avg (This Year)
No incidents recorded for Turkish Airlines in 2026.
Incident History - AerCap (X = Date, Y = Severity)
AerCap cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Turkish Airlines (X = Date, Y = Severity)
Turkish Airlines cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

AerCap

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