CVE-2019-16248 json
The "delete for" feature in Telegram before 5.11 on Android does not delete shared media files from the Telegram Images directory.
published 2019-09-11 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-7055
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 38%
- public exploits
- 0
- none known
Summary
The "delete for" feature in Telegram before 5.11 on Android does not delete shared media files from the Telegram Images directory. In other words, there is a potentially misleading UI indication that a sender can remove a recipient's copy of a previously sent image (analogous to supported functionality in which a sender can remove a recipient's copy of a previously sent message).
Patch / fix
- telegram telegram 5.11.0
Exploit prediction
0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- inputzero.io https://www.inputzero.io/2019/09/telegram-privacy-fails-again.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
References
-
inputzero.io
/2019/09/telegram-privacy-fails-again.html
exploit, third-party-advisory
-
github.com
/RootUp/PersonalStuff/blob/master/Telegram_Privacy.pdf
third-party-advisory
-
openwall.com
/lists/oss-security/2019/09/09/2
mailing-list, third-party-advisory
Sources
- CVE List CVE-2019-16248
- NVD CVE-2019-16248
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.