Telegram

Submit a proposal Propose CVE/GCVE/GHSA reference

Approved changes feed: RSS · Atom

cpe:2.3:a:telegram:telegram:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorTelegram (b9f5ed6a-4116-5a84-8f1b-e541cba3a9c1)
ProductTelegram (af2ee54b-0f3a-5198-8955-04c03dd0e40c)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/drklo/telegram purl2cpe 2026-06-01 10:13:08.344997

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2021-27205 vulnerable 2026-06-08 05:30:46.072961 Details available
Telegram before 7.4 (212543) Stable on macOS stores the local copy of self-destructed messages in a sandbox path, leading to sensitive information disclosure.
Published: 2021-02-12T07:48:39.000Z
Updated: 2024-08-03T20:40:47.392Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2021-27204 vulnerable 2026-06-08 05:30:46.072524 Details available
Telegram before 7.4 (212543) Stable on macOS stores the local passcode in cleartext, leading to information disclosure.
Published: 2021-02-12T07:48:51.000Z
Updated: 2024-08-03T20:40:47.413Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2019-10044 vulnerable 2026-06-08 05:12:21.940355 Details available
Telegram Desktop before 1.5.12 on Windows, and the Telegram applications for Android, iOS, and Linux, is vulnerable to an IDN homograph attack when displaying messages containing URLs. This occurs because the application produces a clickable link even if (for example) Latin and Cyrillic characters exist in the same domain name, and the available font has an identical representation of characters from different alphabets.
Published: 2019-03-25T19:29:17.000Z
Updated: 2024-08-04T22:10:09.354Z
Reference links
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.