Comparison Overview
AVIOBOOK

AVIOBOOK
Herkenrodesingel, Hasselt, 3500, BE
Last Update: 02/04/2026
AVIOBOOK, a Thales Group company, supports airlines as a partner in their digital strategy. AVIOBOOK offers a comprehensive and highly integrated suite of ground and flight applications, systems and solutions that connect all stakeholders and key assets in a safe and ...

Alaska Airlines
19300 International Blvd, Seattle, 98188, US
Last Update: 14/09/2026
We’re creating an airline people love. It begins with each Alaska Airlines employee, bringing unique strengths and energy to our work in the air and on the ground. Every day, we go beyond what’s expected and reach for the remarkable, together. Welcome to our LinkedIn ...
Compliance Ranges Comparison

AVIOBOOK







Alaska Airlines






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

AVIOBOOK

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