Comparison Overview
Lufthansa Cargo

Lufthansa Cargo
Lufthansa Cargo AG Frankfurt Flughafen, Frankfurt am Main, 60546, DE
Last Update: 16/03/2026
With revenue of 3.26 billion euros and a transport performance of 8.48 billion freight ton kilometers in 2024, Lufthansa Cargo is one of the world's leading companies in the transport of airfreight. The company currently employs around 4,250 people worldwide. Lufthansa ...

Qantas
10 Bourke Road, Mascot, 2020, AU
Last Update: 24/09/2026
We would like to acknowledge the Traditional Custodians of the local lands and waterways on which we live, work and fly. We pay our respects to Elders past and present. Spirit is everything to us, and joining the Qantas team means bringing your spirit to ours. We have...
Compliance Ranges Comparison

Lufthansa Cargo







Qantas






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

Lufthansa Cargo

Qantas
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)