CVE-2020-12474

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.

Published: 2020-05-01 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-12474 is rated Moderate Risk (56.5/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 2.53%). EPSS rose +1.57% over the last day, indicating growing attacker interest. Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-12474

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.96% 2.53% +1.57%
2 2026-02-14 0.80% 0.96% +0.17%
3 2025-11-21 — 0.80% —

Full EPSS history (15 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-12474

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 3.6 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2020-12474

OS Trackers for CVE-2020-12474

vendor priority summary link
debian not yet assigned CVE-2020-12474 not yet assigned priority: Debian including 1 source packages (telegram-desktop), 4 status rows across 4 suites (bookworm, bullseye, forky, sid): resolved 4. https://security-tracker.debian.org/tracker/CVE-2020-12474
ubuntu medium CVE-2020-12474 medium priority: Ubuntu including 1 source packages (telegram-desktop), 17 status rows across 17 suites (bionic, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 8, not-affected 5, needs-triage 3, ignored 1. https://ubuntu.com/security/CVE-2020-12474

Affected software / configurations for CVE-2020-12474

Vendor Product Version Raw CPE
telegram telegram <= 6.0.1 cpe:2.3:a:telegram:telegram:*:*:*:*:*:android:*:*
telegram telegram <= 6.0.1 cpe:2.3:a:telegram:telegram:*:*:*:*:*:iphone_os:*:*
telegram telegram_desktop <= 2.0.1 cpe:2.3:a:telegram:telegram_desktop:*:*:*:*:*:*:*:*

References for CVE-2020-12474

cvelogic Threat Intelligence