Comparison Overview
Allegiant

Allegiant
1201 N. Town Center Drive, Las Vegas, NV, US, 89144
Last Update: 04/04/2026
Las Vegas-based Allegiant (NASDAQ: ALGT) is focused on linking travelers in small cities to world-class leisure destinations. The airline offers industry-low fares on an all-jet fleet while also offering other travel-related products such as hotel rooms and rental cars....

Qantas
10 Bourke Road, Mascot, 2020, AU
Last Update: 07/10/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

Allegiant







Qantas






Benchmark & Cyber Underwriting Signals
Incidents vs Airlines and Aviation Industry Avg (This Year)
No incidents recorded for Allegiant 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 - Allegiant (X = Date, Y = Severity)
Allegiant 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

Allegiant

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