CVE-2020-25824 json
Telegram Desktop through 2.4.3 does not require passcode entry upon pushing the Export key within the Export Telegram Data wizard.
published 2020-10-14 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-18460
- cvss
- 2.4
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 46%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Exploit prediction
0.55% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 2.4 | CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-306 Missing Authentication for Critical Functionality
References
-
security.gentoo.org
/glsa/202101-34
vendor-advisory, third-party-advisory
-
telegram.org
product
-
github.com
/soheilsamanabadi/vulnerability/blob/main/Telegram-Desktop-CVE-2020-25824
third-party-advisory
-
github.com
/telegramdesktop/tdesktop/releases/tag/v2.4.3
release-notes, third-party-advisory
Sources
- CVE List CVE-2020-25824
- NVD CVE-2020-25824
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.