Comparison Overview
Flightradar24

Flightradar24
N/A
Last Update: 01/04/2026
Flightradar24 tracks positions of aircraft in real-time and turns that data into engaging consumer and business applications. The data comes primarily from a proprietary, crowd-sourced network of 40,000+ so-called ADS-B receivers hosted by private individuals and compan...

IndiGo (InterGlobe Aviation Ltd)
Level 1, Tower C, Global Business Park,, Gurgaon, 122 002, IN
Last Update: 07/10/2026
IndiGo is India’s largest passenger airline. We operate with focus on our three pillars – offering low fares, being on-time and delivering a courteous and hassle-free experience. IndiGo has become synonymous with being on-time. Since our inception in August 2006, we ha...
Compliance Ranges Comparison

Flightradar24







IndiGo (InterGlobe Aviation Ltd)






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

Flightradar24

IndiGo (InterGlobe Aviation Ltd)
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.