Comparison Overview
Lufthansa Aviation Training Group

Lufthansa Aviation Training Group
Südallee 15, München-Flughafen, Bayern, 85356, DE
Last Update: 27/02/2026
Lufthansa Aviation Training GmbH (LAT) is a subsidiary of Lufthansa Commercial Holding GmbH which is headquartered in Munich, Germany. The company emerged at the beginning of 2017 from the amalgamation of the present Lufthansa Flight Training and Swiss AviationTraining....

Delta Air Lines
1030 Delta Boulevard, Atlanta, Georgia, US, 30320-6001
Last Update: 15/08/2026
Delta Air Lines (NYSE: DAL) is the U.S. global airline leader in safety, innovation, reliability and customer experience. Powered by our employees around the world, Delta has for a decade led the airline industry in operational excellence while maintaining our reputatio...
Compliance Ranges Comparison

Lufthansa Aviation Training Group







Delta Air Lines






Benchmark & Cyber Underwriting Signals
Incidents vs Airlines and Aviation Industry Avg (This Year)
No incidents recorded for Lufthansa Aviation Training Group in 2026.
Incidents vs Airlines and Aviation Industry Avg (This Year)
Delta Air Lines has 94.17% more incidents than the average of all companies with at least one recorded incident.
Incident History - Lufthansa Aviation Training Group (X = Date, Y = Severity)
Lufthansa Aviation Training Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Delta Air Lines (X = Date, Y = Severity)
Delta Air Lines cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Lufthansa Aviation Training Group

Delta Air Lines
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.