VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

telegram-desktop: vulnerability history, versions and safety

telegram-desktop is a package in the Debian ecosystem. Vulert records 20 vulnerabilities for it across 67 releases, from May 2017 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
20 vulnerabilities recorded U20
i
6 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
2 in the last 12 months

Most recent disclosure 03 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all telegram-desktop vulnerabilities

Vulert verdict on telegram-desktop i

Updated on 23 Oct 2026

Careful: 6 of the 20 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 20 vulnerabilities on record across 9 years, 2 in the last year.

What to do: Plan around the 6 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 20 over 9 years · 2 in the last year i
  • Latest disclosure 03 May 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 6 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for telegram-desktop, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
5.7.2+ds-5 U1 No Details →
5.7.2+ds-4 U2 No Details →
5.7.2+ds-3 U2 No Details →
5.7.2+ds-2 U2 No Details →
5.7.2+ds-2~bpo13+1 U1 No Details →
4.14.9+ds-1.1 U6 No Details →
4.14.9+ds-1 U6 No Details →
4.14.4+ds-1 U6 No Details →
4.14.3+ds-1 U6 No Details →
4.13.1+ds-1 U6 No Details →
4.11.8+ds-1 U6 No Details →
4.11.5+ds-1 U6 No Details →
4.10.3+ds-2 U6 No Details →
4.10.3+ds-1 U6 No Details →
4.9.7+ds-1 U6 No Details →
4.9.3+ds-1 U6 No Details →
4.8.1+ds-2 U6 No Details →
4.8.1+ds-2~bpo12+1 U6 No Details →
4.8.1+ds-2~bpo11+1 U6 No Details →
4.8.1+ds-1 U6 No Details →
4.6.5+ds-2 U6 No Details →
4.6.5+ds-1 U6 No Details →
4.6.5+ds-1~bpo11+1 U6 No Details →
4.6.2+ds-1 U6 No Details →
4.6.0+ds-1 U6 No Details →
4.5.3+ds-1 U6 No Details →
4.5.3+ds-1~bpo11+1 U6 No Details →
4.4.1+ds-1 U6 No Details →
4.4.1+ds-1~bpo11+1 U6 No Details →
4.3.4+ds-2 U6 No Details →
4.3.4+ds-1 U6 No Details →
4.3.1+ds-1 U6 No Details →
4.3.1+ds-1~bpo11+1 U6 No Details →
4.2.4+ds-1 U6 No Details →
4.2.4+ds-1~bpo11+1 U6 No Details →
4.2.0+ds-1 U6 No Details →
4.1.1+ds-1 U6 No Details →
4.1.0+ds-1 U6 No Details →
4.0.2+ds-2 U6 No Details →
4.0.2+ds-1 U6 No Details →
3.7.3+ds-2 U6 No Details →
3.7.3+ds-1 U6 No Details →
3.7.1+ds-1 U6 No Details →
3.6.1+ds-3 U6 No Details →
3.6.1+ds-2 U6 No Details →
3.6.1+ds-1 U6 No Details →
3.6.0+ds-1 U6 No Details →
3.5.2+ds-1 U6 No Details →
3.5.2+ds-1~bpo11+1 U6 No Details →
3.4.8+ds-1 U6 No Details →
3.4.3+ds-1 U6 No Details →
3.4.3+ds-1~bpo11+1 U6 No Details →
3.4.2+ds-1 U6 No Details →
3.3.0+ds-2 U6 No Details →
3.3.0+ds-1 U6 No Details →
3.1.8+ds-1 U6 No Details →
3.1.1+ds-1 U6 No Details →
3.1.1+ds-1~bpo11+1 U6 No Details →
3.1.1+ds-1~deb11u2 U6 No Details →
3.1.1+ds-1~bpo10+1 U6 No Details →
2.9.2+ds-1 U6 No Details →
2.9.2+ds-1~bpo11+1 U8 No Details →
2.9.2+ds-1~bpo10+1 U8 No Details →
2.9.0+ds1-2 U8 No Details →
2.9.0+ds-1 U8 No Details →
2.6.1+ds-1 U8 No Details →
2.6.1+ds-1+deb11u1 U8 No Details →

Newest 67 of 67 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 2
  • 2018 6
  • 2019 2
  • 2020 4
  • 2021 4
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 20 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for telegram-desktop

The 5 most severe of 20 vulnerabilities recorded for this package

Search all 20 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Clear Text Transmission of Credentials in Telegram Desktop 9.8 critical No fix published 28 Sep 2018
IDN Homograph Attack Vulnerability in Telegram Desktop and Mobile Applications 8.8 high 1.8.4-1 25 Mar 2019
Spoofed File Type Bypass in Telegram Desktop: CVE-2020-17448 7.8 high 2.2.0+ds-1 11 Aug 2020
Denial of Service Vulnerability in Telegram Desktop 7.5 high No fix published 19 Sep 2018
Denial of Service Vulnerability in Telegram Desktop 2.9.2 7.5 high No fix published 16 Jan 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About telegram-desktop

Is telegram-desktop safe to use?

Vulert records 20 vulnerabilities for telegram-desktop in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 20 not yet rated. 6 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does telegram-desktop have?

20 vulnerabilities are recorded for telegram-desktop in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 20 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new telegram-desktop vulnerabilities disclosed?

2 vulnerabilities were recorded for telegram-desktop in the last 12 months, and the oldest entry in this database dates to 01 May 2017. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of telegram-desktop are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor telegram-desktop for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the telegram-desktop version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.