CVE-2026-107181

HIGHPre-NVD 8.18.1
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-10-07. A secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated
8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.1Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.1
EG Score
8.1HIGHhigh confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
26th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 7, 2026

Last Modified

October 7, 2026

Advisory Details (7)

Auto-updated Oct 7, 2026
Patch available. Sources: github_commit, github_release.
Web page

Telegram Desktop before 7.2.9 IPC Record Injection File Exfiltration via interpret: Scheme | Advisories | VulnCheck

https://www.vulncheck.com/advisories/telegram-desktop-before-7.2.9-ipc-record-injection-file-exfiltration-via-interpret-scheme
Web page

GitHub - telegramdesktop/tdesktop: Telegram Desktop messaging app · GitHub

https://github.com/telegramdesktop/tdesktop
Web page

tdesktop/Telegram/SourceFiles/support/support_helper.cpp at v7.2.8 · telegramdesktop/tdesktop · GitHub

https://github.com/telegramdesktop/tdesktop/blob/v7.2.8/Telegram/SourceFiles/support/support_helper.cpp#L673-L751
Web page

tdesktop/Telegram/SourceFiles/core/sandbox.cpp at v7.2.8 · telegramdesktop/tdesktop · GitHub

https://github.com/telegramdesktop/tdesktop/blob/v7.2.8/Telegram/SourceFiles/core/sandbox.cpp#L362-L364
GitHub release Patch Available

v 7.2.9

Patch available: telegramdesktop/tdesktop v7.2.9

https://github.com/telegramdesktop/tdesktop/releases/tag/v7.2.9
GitHub commit

commit db3405699f8f (telegramdesktop/tdesktop)

Fix landed in telegramdesktop/tdesktop commit db3405699f8f — awaiting tagged release

https://github.com/telegramdesktop/tdesktop/commit/db3405699f8fc3ae28a58d2348b7d13a43c0590a
Web page

Telegram Desktop: one-click account takeover via IPC injection | beaksec

https://beaksec.github.io/posts/telegram-desktop-one-click-account-takeover/

Vendor Advisories for CVE-2026-107181(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 2 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
telegram-desktop4.10.3+ds-1 ... 5.7.2+ds-5 (21 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
telegram-desktop1.0.14-1 ... 5.7.2+ds-5 (120 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 27× in last 7d / 27× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-11 22:05 UTCGHSA enrichmentGHSA-2h6w-ccjh-5jhr · GitHub severity HIGH · GitHub CVSS 8.1
  2. 2026-10-11 20:14 UTCEG score recompute
  3. 2026-10-11 18:26 UTCEG score recompute
  4. 2026-10-11 15:00 UTCEG score recompute
  5. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  6. 2026-10-11 10:55 UTCGHSA enrichmentGHSA-2h6w-ccjh-5jhr · GitHub severity HIGH · GitHub CVSS 8.1
  7. 2026-10-10 23:42 UTCEG score recompute
  8. 2026-10-10 23:41 UTCGHSA enrichmentGHSA-2h6w-ccjh-5jhr · GitHub severity HIGH · GitHub CVSS 8.1
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  10. 2026-10-10 12:32 UTCGHSA enrichmentGHSA-2h6w-ccjh-5jhr · GitHub severity HIGH · GitHub CVSS 8.1
  11. 2026-10-10 01:21 UTCEG score recompute
  12. 2026-10-10 01:21 UTCGHSA enrichmentGHSA-2h6w-ccjh-5jhr · GitHub severity HIGH · GitHub CVSS 8.1
  13. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  14. 2026-10-09 14:11 UTCGHSA enrichmentGHSA-2h6w-ccjh-5jhr · GitHub severity HIGH · GitHub CVSS 8.1
  15. 2026-10-09 02:59 UTCEG score recompute
  16. 2026-10-09 02:59 UTCGHSA enrichmentGHSA-2h6w-ccjh-5jhr · GitHub severity HIGH · GitHub CVSS 8.1
  17. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  18. 2026-10-08 15:49 UTCGHSA enrichmentGHSA-2h6w-ccjh-5jhr · GitHub severity HIGH · GitHub CVSS 8.1
  19. 2026-10-08 04:31 UTCEG score recompute
  20. 2026-10-08 04:31 UTCGHSA enrichmentGHSA-2h6w-ccjh-5jhr · GitHub severity HIGH · GitHub CVSS 8.1
  21. 2026-10-07 17:20 UTCEG score recompute
  22. 2026-10-07 17:19 UTCGHSA enrichmentGHSA-2h6w-ccjh-5jhr · GitHub severity HIGH · GitHub CVSS 8.1
  23. 2026-10-07 16:13 UTCEG score recompute
  24. 2026-10-07 16:12 UTCGHSA enrichmentGHSA-2h6w-ccjh-5jhr · GitHub severity HIGH · GitHub CVSS 8.1
  25. 2026-10-07 14:28 UTCEG score recompute
Show 2 more
  1. 2026-10-07 13:52 UTCEG score recomputeFirst assessed: 8.1 HIGH
  2. 2026-10-07 13:51 UTCMITRE cvelistV5first tracked

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCSeanDishman/telegram-cve-2026-107181
    Published Oct 10, 2026

    Telegram CVE-2026-107181

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-107181?
CVE-2026-107181 is a high-severity vulnerability; its CVE record was published on October 7, 2026. 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…
When was CVE-2026-107181 made public?
CVE-2026-107181 was made public on September 16, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 7, 2026. EchelonGraph's copy of the record carries a last-modified date of October 7, 2026; the record at its source may have been updated since.
Is CVE-2026-107181 actively exploited?
CVE-2026-107181 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-107181?
CVE-2026-107181 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-107181?
A fix for CVE-2026-107181 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-107181 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-107181

Explore →

Is Your Infrastructure Affected by CVE-2026-107181?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs