Comparison Overview
Delta Technology Hub

Delta Technology Hub
2nd Floor, L1, Banyan Block, Bengaluru, 560045, IN
Last Update: 04/04/2026
Delta Air Lines is at the forefront of disruption in the airline industry and the teams at Delta Technology Hub are playing a key role in shaping the future of aviation. By working on innovative products for millions of customers, the teams at DTH are not only transform...

Southwest Airlines
2702 Love Field Drive, Dallas, TX, US, 75235
Last Update: 12/10/2026
At Southwest®, everything we do—from our smiling People to our policies—is designed to let you go with Heart. No matter what comes up in your travels, we’ve got your back. Because while any airline can fly you, only Southwest lets you go with Heart. Application fees do...
Compliance Ranges Comparison

Delta Technology Hub







Southwest Airlines






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

Delta Technology Hub

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