Telegram Desktop
Approved changes feed: RSS · Atom
cpe:2.3:a:telegram:telegram_desktop:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Telegram (b9f5ed6a-4116-5a84-8f1b-e541cba3a9c1) |
|---|---|
| Product | Telegram Desktop (298ff4b3-acf4-5b60-88a9-548cd82dcd54) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/telegramdesktop/tdesktop |
purl2cpe | 2026-06-01 10:13:08.391835 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-94488 |
vulnerable | 2026-10-13 12:28:38.906019 |
Details available
HIGH (8.2)
Telegram Desktop before 6.9.4 allows XSS in the HTML exporter. (The first fixed stable version is 7.0.1.) This occurs in button.text.toUtf8 in export_output_html.cpp. Exploitation cannot occur unless HTML export was used by a victim. However, the exploit payload can be exported if a message were forwarded into a group by a member (it is not necessary for the message author to be a member of a group).
Published: 2026-09-21T17:29:01.776Z
Updated: 2026-09-21T17:51:18.874Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-47793 |
vulnerable | 2026-06-08 05:38:07.673140 |
Telegram Desktop 2.9.2 - Denial of Service (PoC)
HIGH (7.5)
Telegram Desktop 2.9.2 contains a denial of service vulnerability that allows attackers to crash the application by sending an oversized message payload. Attackers can generate a 9 million byte buffer and paste it into the messaging interface to trigger an application crash.
Published: 2026-01-15T23:25:43.035Z
Updated: 2026-03-05T01:28:35.818Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-36769 |
vulnerable | 2026-06-08 05:32:52.491637 |
Details available
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-16T23:03:50.000Z
Updated: 2024-08-04T01:01:59.025Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-25824 |
vulnerable | 2026-06-08 05:23:49.477049 |
Details available
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-14T14:10:51.000Z
Updated: 2024-08-04T15:40:36.989Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-17448 |
vulnerable | 2026-06-08 05:20:56.499026 |
Details available
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-11T16:02:42.000Z
Updated: 2024-08-04T13:53:17.527Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-12474 |
vulnerable | 2026-06-08 05:17:58.242548 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2019-10044 |
vulnerable | 2026-06-08 05:12:21.941082 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.