VendorsTelegramtelegram_desktopall versions
Vulnerabilities

Telegram Telegram Desktop

Ranked by severity, then by exploit likelihood. Click a CVE ID for its full record.

9CVEs
CVE-2018-17613
Telegram Desktop (aka tdesktop) 1.3.16 alpha, when "Use proxy" is enabled, sends credentials and application data in cleartext over the SOCKS5 protocol.
Published 2018-09-28 · Modified
9.8EPSS 0.016
CVE-2019-10044
Telegram Desktop before 1.5.12 on Windows, and the Telegram applications for Android, iOS, and Linux, is vulnerable to an IDN homograph attack when displaying messages containing URLs. This occurs because the application produces a clickable link even if (for example) Latin and Cyrillic characters exist in the same domain name, and the available font has an identical representation of characters from different alphabets.
Published 2019-03-25 · Modified
8.8EPSS 0.033
CVE-2020-17448
Telegram Desktop through 2.1.13 allows a spoofed file type to bypass the Dangerous File Type Execution protection mechanism, as demonstrated by use of the chat window with a filename that lacks an extension.
Published 2020-08-11 · Modified
7.8EPSS 0.023
CVE-2018-17231
Telegram Desktop (aka tdesktop) 1.3.14 might allow attackers to cause a denial of service (assertion failure and application exit) via an "Edit color palette" search that triggers an "index out of range" condition. NOTE: this issue is disputed by multiple third parties because the described attack scenario does not cross a privilege boundary
Published 2018-09-19 · Modified
7.5EPSS 0.015
CVE-2021-47793
Telegram Desktop 2.9.2 - Denial of Service (PoC)
Published 2026-01-15 · Analyzed
7.5EPSS 0.005
CVE-2020-12474
Telegram Desktop through 2.0.1, Telegram through 6.0.1 for Android, and Telegram through 6.0.1 for iOS allow an IDN Homograph attack via Punycode in a public URL or a group chat invitation URL.
Published 2020-05-01 · Modified
6.5EPSS 0.026
CVE-2018-17780
Telegram Desktop (aka tdesktop) 1.3.14, and Telegram 3.3.0.0 WP8.1 on Windows, leaks end-user public and private IP addresses during a call because of an unsafe default behavior in which P2P connections are accepted from clients outside of the My Contacts list.
Published 2018-09-29 · Modified
6.5EPSS 0.018
CVE-2021-36769
A reordering issue exists in Telegram before 7.8.1 for Android, Telegram before 7.8.3 for iOS, and Telegram Desktop before 2.8.8. An attacker can cause the server to receive messages in a different order than they were sent a client.
Published 2021-07-16 · Modified
5.3EPSS 0.014
CVE-2020-25824
Telegram Desktop through 2.4.3 does not require passcode entry upon pushing the Export key within the Export Telegram Data wizard. The threat model is a victim who has voluntarily opened Export Wizard but is then distracted. An attacker then approaches the unattended desktop and pushes the Export key. This attacker may consequently gain access to all chat conversation and media files.
Published 2020-10-14 · Modified
2.4EPSS 0.006