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

> A remote attacker can cause a one-time crash in Telegram Desktop via a null pointer dereference in the Bot API, though the vendor disputes its security impact.

- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 May 2026
- **Updated:** 19 May 2026
- **Also known as:** DEBIAN-CVE-2026-7701, GHSA-8hhg-crp9-v482, UBUNTU-CVE-2026-7701

## What is CVE-2026-7701?

CVE-2026-7701 is a medium-severity vulnerability in Telegram Desktop, published on 3 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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

Weakness: CWE-476 (NULL Pointer Dereference), CWE-404 (Improper Resource Shutdown or Release)

## Which versions are affected by CVE-2026-7701?


## How do I fix CVE-2026-7701?

No fix has been published for CVE-2026-7701 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-7701 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7701 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7701 and fix it if it is affected.

What it is: CVE-2026-7701 is a medium-severity vulnerability in Telegram Desktop, published on 3 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7701 exists.

Affected product: Telegram Desktop. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-7701/ (Markdown: https://insights.sbomify.com/CVE-2026-7701/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-7701
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-7701
- OSV: https://osv.dev/vulnerability/CVE-2026-7701

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-7701/
Summaries are generated and may contain mistakes; the official description above is the record.