Comparison Overview
Telegram Messenger

Telegram Messenger
Business Central Towers, Tower A, Dubai, 501919, AE
Last Update: 25/09/2026
Pure instant messaging — simple, fast, secure, and synced across all your devices.

Personal
Calle General Hornos 690, Comuna 1, Ciudad Autónoma de Buenos Aires, AR, 1272
Last Update: 27/09/2026
En Personal, ponemos a las personas en el centro. Somos el ecosistema de servicios de Telecom Argentina S.A. que conecta a cada persona con todo lo que le importa. Nuestra propuesta está pensada para que cada persona, comunidad y organización pueda avanzar, disfrutar y ...
Compliance Ranges Comparison

Telegram Messenger







Personal






Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
Telegram Messenger has 707.45% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Personal in 2026.
Incident History - Telegram Messenger (X = Date, Y = Severity)
Telegram Messenger cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Personal (X = Date, Y = Severity)
Personal cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Telegram Messenger

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