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.

published 2021-07-16 5y ago modified 2026-06-17 4mo ago also EUVD-2021-23357

cvss: 5.3; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.4%; EPSS 1.4% chance of exploitation in 30 days, percentile 72%
public exploits: 0; none known

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.

Patch / fix

fixed in 2 distros 2

telegram telegram 7.8.1, 7.8.3
telegram telegram_desktop 2.8.8

debian arch linux

telegram-desktop Debian 14, Debian 12 2.9.2+ds-1

debian advisories DEBIAN-CVE-2021-36769

telegram-desktop Arch Linux 2.8.11-1

arch linux advisories AVG-2170

Is CVE-2021-36769 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.39% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:P/A:N

References

mtpsym.github.io
technical-description, third-party-advisory

Sources

CVE List CVE-2021-36769
NVD CVE-2021-36769

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.