CVE-2021-36769

A reordering issue exists in Telegram before 7.8.1 for Android, Telegram before 7.8.3 for iOS, and Telegram Desktop before 2.8.8. An attacker can cause the server to receive messages in a different order than they were sent a client.

Published: 2021-07-17 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2021-36769 is rated Low Risk (39.1/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.29%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

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-2021-36769

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 2025-03-17 0.07% 0.29% +0.22%
2 2023-03-07 0.89% 0.07% -0.81%
3 2022-04-01 — 0.89% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2021-36769

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 1.4 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:N/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2021-36769

OS Trackers for CVE-2021-36769

vendor priority summary link
debian not yet assigned CVE-2021-36769 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-2021-36769
ubuntu medium CVE-2021-36769 medium priority: Ubuntu including 1 source packages (telegram-desktop), 16 status rows across 16 suites (bionic, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 7, ignored 5, needs-triage 4. https://ubuntu.com/security/CVE-2021-36769

Affected software / configurations for CVE-2021-36769

Vendor Product Version Raw CPE
telegram telegram < 7.8.1 cpe:2.3:a:telegram:telegram:*:*:*:*:*:android:*:*
telegram telegram < 7.8.3 cpe:2.3:a:telegram:telegram:*:*:*:*:*:iphone_os:*:*
telegram telegram_desktop < 2.8.8 cpe:2.3:a:telegram:telegram_desktop:*:*:*:*:*:*:*:*

References for CVE-2021-36769

URL Tags
https://mtpsym.github.io Technical Description Third Party Advisory
cvelogic Threat Intelligence