CVE-2019-16248
The "delete for" feature in Telegram before 5.11 on Android does not delete shared media files from the Telegram Images directory.
Does this matter?
Lower severity and a low EPSS score (0.44%). Track it; it rarely justifies an emergency change on its own.
Description
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).
- CVSS 3.1
- 5.5 MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- EPSS
- 0.44% probability · 38th percentile
- Public exploits
- None in Exploit-DB
- CISA KEV
- Not listed
- Affected
- telegram/telegram
- Source
- cve@mitre.org
EPSS 0.4% since 26 October 2026; no change recorded yet. Points are recorded when the score first appears and whenever it moves by a percentage point or more.
References
- https://github.com/RootUp/PersonalStuff/blob/master/Telegram_Privacy.pdfThird Party Advisory
- https://www.inputzero.io/2019/09/telegram-privacy-fails-again.htmlExploit, Third Party Advisory
- https://www.openwall.com/lists/oss-security/2019/09/09/2Mailing List, Third Party Advisory
- https://github.com/RootUp/PersonalStuff/blob/master/Telegram_Privacy.pdfThird Party Advisory
- https://www.inputzero.io/2019/09/telegram-privacy-fails-again.htmlExploit, Third Party Advisory
- https://www.openwall.com/lists/oss-security/2019/09/09/2Mailing List, Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.