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-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 |
Details available
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-01T13:45:28.000Z
Updated: 2024-08-04T11:56:52.071Z |
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.