Vulnerabilities (CVE)

Filtered by vendor Telegram Subscribe
Filtered by product Telegram
Total 27 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2021-31315 1 Telegram 1 Telegram 2024-11-21 4.3 MEDIUM 5.5 MEDIUM
Telegram Android <7.1.0 (2090), Telegram iOS <7.1, and Telegram macOS <7.1 are affected by a Stack Based Overflow in the blit function of their custom fork of the rlottie library. A remote attacker might be able to access Telegram's stack memory out-of-bounds on a victim device via a malicious animated sticker.
CVE-2021-30496 1 Telegram 1 Telegram 2024-11-21 3.5 LOW 5.7 MEDIUM
The Telegram app 7.6.2 for iOS allows remote authenticated users to cause a denial of service (application crash) if the victim pastes an attacker-supplied message (e.g., in the Persian language) into a channel or group. The crash occurs in MtProtoKitFramework. NOTE: the vendor's perspective is that "this behavior can't be considered a vulnerability."
CVE-2021-27351 1 Telegram 1 Telegram 2024-11-21 5.0 MEDIUM 5.3 MEDIUM
The Terminate Session feature in the Telegram application through 7.2.1 for Android, and through 2.4.7 for Windows and UNIX, fails to invalidate a recently active session.
CVE-2021-27205 2 Apple, Telegram 2 Macos, Telegram 2024-11-21 2.1 LOW 5.5 MEDIUM
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.
CVE-2021-27204 2 Apple, Telegram 2 Macos, Telegram 2024-11-21 2.1 LOW 5.5 MEDIUM
Telegram before 7.4 (212543) Stable on macOS stores the local passcode in cleartext, leading to information disclosure.
CVE-2020-12474 1 Telegram 2 Telegram, Telegram Desktop 2024-11-21 4.3 MEDIUM 6.5 MEDIUM
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.
CVE-2020-10570 1 Telegram 1 Telegram 2024-11-21 3.6 LOW 6.1 MEDIUM
The Telegram application through 5.12 for Android, when Show Popup is enabled, might allow physically proximate attackers to bypass intended restrictions on message reading and message replying. This might be interpreted as a bypass of the passcode feature.