Skip to main content

Telegram Desktop CVE-2026-7701

| EUVDEUVD-2026-26839 LOW
NULL Pointer Dereference (CWE-476)
2026-05-03 VulDB
2.1
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Attacker crafts malicious login_url parameter
  2. Delivery
    Sends link via Telegram message
  3. Exploit
    User clicks malicious link
  4. Install
    RequestButton function processes login_url
  5. C2
    Null pointer dereference in url_auth_box.cpp
  6. Execute
    Telegram Desktop crashes
  7. Impact
    User experiences denial of service

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V16 - Security Logging and Error Handling Null pointer safety, defensive checks
MITRE ATT&CK

1 technique across 1 tactic: Impact

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

User must click a malicious link or interact with a crafted Telegram message containing the specially formatted login_url parameter. The vulnerability is triggered within the Bot API RequestButton function when processing the login_url argument, so the user's Telegram Desktop client must attempt to process this parameter. No authentication is required from the attacker's perspective, and the attack is remotely deliverable via Telegram's messaging infrastructure. The vulnerability exists by default in affected versions without requiring non-standard configuration. Exploitation is limited by the requirement for user interaction-the application crash only occurs if the user clicks the malicious link or if Telegram Desktop automatically processes the parameter in certain message contexts.

Impact

This vulnerability presents a moderate real-world risk with several mitigating factors. The CVSS score of 4.3 reflects low severity, driven by the requirement for user interaction (UI:R) and limited impact scope (denial of service only, with no confidentiality or integrity compromise). The CVSS vector shows network attack surface (AV:N/AC:L/PR:N) but mandatory user engagement (UI:R) significantly reduces practical exploit likelihood. EPSS scoring data is not provided, but the public exploit disclosure (E:P) and reliable reproduction (RC:R) suggest the vulnerability is technically feasible. However, the absence of authentication requirements and network vector are offset by the user-interaction prerequisite-an attacker must socially engineer a user to click a crafted link. The impact is limited to availability (denial of service via application crash), not system compromise. The vendor's non-response to early disclosure (per description) raises concern about patch availability but does not elevate the technical severity. This is a legitimate priority for desktop application users but not a critical infrastructure threat; prioritize based on user base exposure and whether user awareness training can mitigate the social engineering vector.

Exploit ScenarioDerived

An attacker crafts a malicious Telegram message or web link containing a specially formatted login_url parameter that, when clicked by a user, triggers the RequestButton function in Telegram Desktop. The null pointer dereference in url_auth_box.cpp causes the application to crash, resulting in denial of service for that user. The attacker could distribute this link via Telegram channels, social engineering, or embedding it in web pages to target multiple users, causing widespread application crashes among victims who interact with the link.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 03, 2026

Null pointer dereference in Telegram Desktop up to version 6.7.5 allows remote attackers without authentication to cause denial of service by crafting a malicious login_url argument in the Bot API RequestButton function. The vulnerability requires user interaction to click a malicious link and has a public exploit disclosure, though vendor response to early disclosure notification was not forthcoming.

RemediationAI

Users should upgrade Telegram Desktop to a version newer than 6.7.5 as soon as a patched release becomes available; however, no specific fixed version number has been independently confirmed from vendor sources at the time of this analysis. Users should avoid clicking suspicious links, especially those requesting Bot API authorization or login confirmation, as these are the primary attack vector. Until a patch is released, consider disabling automatic link opening in Telegram Desktop settings and enabling manual confirmation for any Bot API authorization requests. Administrators managing Telegram Desktop deployments should monitor vendor announcements for patch releases and enforce upgrades through managed software deployment once patches are confirmed available. The vendor's documented non-responsiveness to early disclosure suggests monitoring community forums and security databases (VulDB, NVD) for patch availability rather than relying on official vendor bulletins.

Affected VersionsENISA

Desktop 6.7.4
Desktop 6.7.1
Desktop 6.7.0
Desktop 6.7.3
Desktop 6.7.5
Desktop 6.7.2

Affected Packages

euvd desktop no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability exists in the RequestButton function within Telegram/SourceFiles/boxes/url_auth_box.cpp of the Telegram Desktop Bot API component. The flaw is a null pointer dereference (CWE-476) triggered when the login_url parameter is manipulated. When a null pointer is dereferenced during request processing, the application crashes rather than gracefully handling the malformed input. This is a memory safety issue where input validation or null-check assertions on the login_url argument are insufficient before dereferencing the pointer in downstream code.

Know when Telegram gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 2.1 LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Primary rating from Vendor (VulDB) · only source for this CVE.

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
Passive
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
None
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

3
Severity Changed
May 03, 2026 - 16:22 NVD
MEDIUM LOW
CVSS changed
May 03, 2026 - 16:22 NVD
4.3 (MEDIUM) 2.1 (LOW)
CVE Published
May 03, 2026 - 15:30 nvd
LOW 2.1

DescriptionCVE.org

A security vulnerability has been detected in Telegram Desktop up to 6.7.5. This vulnerability affects the function RequestButton of the file Telegram/SourceFiles/boxes/url_auth_box.cpp of the component Bot API. The manipulation of the argument login_url leads to null pointer dereference. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Threat Intelligence Overview

EPSS Score
0.0%
Top 90% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Low
Technical Impact
Partial

Priority Score

10
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +10
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A null pointer dereference occurs when a program attempts to access memory through a pointer that has been set to NULL (address 0x0).

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

CVE-2019-10044 HIGH POC
8.8 Mar 25

Telegram Desktop before 1.5.12 on Windows, and the Telegram applications for Android, iOS, and Linux, is vulnerable to a

CVE-2026-107181 HIGH POC
8.6 Oct 07

One-click account takeover in Telegram Desktop before 7.2.9, where the Core::Sandbox inter-process communication layer f

CVE-2026-94488 HIGH POC
8.3 Sep 21

Telegram Desktop before 6.9.4 fails to escape inline-keyboard button text when a chat is exported to HTML, so attacker-c

CVE-2018-20436 HIGH POC
8.1 Dec 24

The "secret chat" feature in Telegram 4.9.1 for Android has a "side channel" in which Telegram servers send GET requests

CVE-2021-47793 HIGH POC
7.5 Jan 16

Telegram Desktop versions up to 2.9.2 is affected by allocation of resources without limits or throttling (CVSS 7.5).

CVE-2018-17231 HIGH POC
7.5 Sep 19

Telegram Desktop (aka tdesktop) 1.3.14 might allow attackers to cause a denial of service (assertion failure and applica

CVE-2021-31321 HIGH POC
7.1 May 18

Telegram Android <7.1.0 (2090), Telegram iOS <7.1, and Telegram macOS <7.1 are affected by a Stack Based Overflow in the

CVE-2021-31320 HIGH POC
7.1 May 18

Telegram Android <7.1.0 (2090), Telegram iOS <7.1, and Telegram macOS <7.1 are affected by a Heap Buffer Overflow in the

CVE-2018-17780 MEDIUM POC
6.5 Sep 29

Telegram Desktop (aka tdesktop) 1.3.14, and Telegram 3.3.0.0 WP8.1 on Windows, leaks end-user public and private IP addr

CVE-2022-43363 MEDIUM POC
6.1 Dec 06

Telegram Web 15.3.1 allows XSS via a certain payload derived from a Target Corporation website. Rated medium severity (C

CVE-2021-40532 CRITICAL
9.8 Sep 06

Telegram Web K Alpha before 0.7.2 mishandles the characters in a document extension. Rated critical severity (CVSS 9.8),

CVE-2018-17613 CRITICAL
9.8 Sep 28

Telegram Desktop (aka tdesktop) 1.3.16 alpha, when "Use proxy" is enabled, sends credentials and application data in cle

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy