Medium Denial of service

CVE-2026-7701 — Telegram Desktop Bot API url_auth_box.cpp RequestButton null pointer dereference

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. There is ongoing doubt regarding the real existence of this vulnerability. Upgrading to version 6.7.6 is able to resolve this issue. Upgrading the affected component is recommended. The vendor provides this rationale for the dispute: "[T]he described scenario does not lead to any security issue or vulnerability, and only causes a one-time crash. In the outlined scenario, the targeted user must perform an active action, which doesn't produce any consequences after the app is relaunched."

Published May 3, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulDB

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.5% (30-day exploitation probability)+6
Technical severity (medium)+3
CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.51%

ahead of 42% of scored CVEs · Oct 14, 2026

Affects

Telegram Desktop

CVSS base

4.3

Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

Proof of concept

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Telegram Telegram Desktop).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Exploitation requires user interaction: tighten email/web filtering and warn affected users.
Search available logs for exploit probes matching the vulnerability class (denial of service), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Telegram	Telegram Desktop	version 6.7.0version 6.7.1version 6.7.2version 6.7.3version 6.7.4version 6.7.5	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

None

User interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

Low

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
5.3	CVSS 4.0	Medium	—	—	VulDB via CVE Program (cve.org) e CISA ADP
2.1	CVSS 4.0	Low	—	—	cna@vuldb.com via NIST National Vulnerability Database
4.3	CVSS 3.1	Medium	2.8	1.4	cna@vuldb.com via NIST National Vulnerability Database
4.3	CVSS 3.1	Medium	—	—	VulDB via CVE Program (cve.org) e CISA ADP
4.3	CVSS 3.0	Medium	—	—	VulDB via CVE Program (cve.org) e CISA ADP
5.0	CVSS 2.0	Medium	10.0	2.9	cna@vuldb.com via NIST National Vulnerability Database
5.0	CVSS 2.0	Medium	—	—	VulDB via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L (score shown at the top: cna@vuldb.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-404 · Improper Resource Shutdown or Release

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.51%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Track CPU/memory spikes and availability drops correlated with request patterns.

web/proxy/WAF logsnetwork IDS/IPSresource metrics

Timeline

What happened to this CVE, newest first.

2026
Affected products added · telegram/desktop
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 4.3
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Deferred
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
May 3, 2026 · VulDB

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

4 on the record

www.youtube.com/watch
media-coverage, NIST National Vulnerability Database
vuldb.com/vuln/360870
vdb-entry, technical-description, NIST National Vulnerability Database
vuldb.com/submit/804341
third-party-advisory, NIST National Vulnerability Database
vuldb.com/vuln/360870/cti
signature, permissions-required, NIST National Vulnerability Database

Elsewhere on this site

Telegram
every CVE for this vendor

Denial of service
same class

CWE-404
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-107181 Telegram Desktop before 7.2.9 IPC Record Injection File Exfiltration via interpret: Scheme 8d
High CVE-2021-47793 Telegram Desktop 2.9.2 - Denial of Service (PoC) Jan 15, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-7701 is "Telegram Desktop Bot API url_auth_box.cpp RequestButton null pointer dereference", rated Medium. It affects Telegram Desktop (Telegram); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.3 describes technical severity. EPSS 0.51% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.