# CVE-2026-107181: Telegram Desktop before 7.2.9 IPC Record Injection File Exfiltration via interpret: Scheme

> Remote attackers can inject IPC records via crafted links to exfiltrate local session keys, leading to account takeover in Telegram Desktop.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **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:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-107181, GHSA-2h6w-ccjh-5jhr, UBUNTU-CVE-2026-107181

## What is CVE-2026-107181?

CVE-2026-107181 is a high-severity vulnerability in Telegram Desktop, published on 7 Oct 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

Telegram Desktop before 7.2.9 contains an IPC record-separator injection vulnerability in Core::Sandbox that allows remote attackers to inject OPEN: records via crafted tg:// links containing unescaped semicolons. Attackers can reach the interpret: scheme handler to upload local files, including tdata session keys, to an attacker channel, enabling account takeover.

Weakness: CWE-143 (Improper Neutralization of Record Delimiters)

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


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

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

## Is CVE-2026-107181 being exploited?

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

Public exploit code:

- Telegram CVE-2026-107181 (github_poc): https://github.com/SeanDishman/telegram-cve-2026-107181
- https://github.com/abdugafforov-bobur/cve-2026-107181-poc (github_poc): https://github.com/abdugafforov-bobur/cve-2026-107181-poc
- CVE-2026-107181 Proof Of Concept for telegram Desktop account take over in windows (github_poc): https://github.com/00nx/telegram-account-takeover-poc

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107181 is a high-severity vulnerability in Telegram Desktop, published on 7 Oct 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-107181 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-107181/ (Markdown: https://insights.sbomify.com/CVE-2026-107181/index.md)
```

## Sources

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

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