← All stories
● Covered by 1 source · 1 reportMedium impact1 neutral

Telegram Android Flaw Allowed Remote Code Execution via Voice Calls

🔄 Updated 8d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Telegram Android flaw allowed remote code execution.
  • Affected versions 8.6.2 through 12.10.3.
  • Fixed in version 12.10.4, released late September.
  • Required user to answer a voice call to trigger.

Vulnerability Details

Security startup NebuSec identified a flaw in Telegram for Android that could enable remote code execution. The vulnerability was present in versions 8.6.2 to 12.10.3 of the application. An attacker with a standard Telegram account could exploit this flaw by initiating a voice call that the victim answered.

Attack Chain and Impact

According to NebuSec, this flaw could be combined with an information-leak bug to escape the Telegram app's sandbox into the Android operating system. Further chaining with an Android root exploit would grant an attacker full control over the victim's phone, including access to messages, microphone, and camera. NebuSec has no evidence of this flaw being exploited in real-world attacks.

Technical Explanation

The flaw resided in the code responsible for processing 'MediaState' messages, which are exchanged during Telegram calls to report microphone status, camera state, and video rotation. The code failed to correctly handle missing fields in these messages, leading to unauthorized memory access. The Hacker News confirmed this vulnerability by reviewing Telegram's published source code for version 12.10.3.

Resolution and User Action

Telegram addressed the vulnerability in version 12.10.4 of its Android application, released in late September. Users are advised to update their Telegram for Android app to version 12.10.4 or later to mitigate the risk. The flaw could also be blocked by setting Telegram's call privacy option to 'Nobody' or by declining incoming calls.

Disclosure and Recognition

NebuSec reported the flaw to Telegram on September 26, after the fix had already been released. Telegram acknowledged the report but did not assign a CVE identifier or issue a bug bounty, as it initially did not believe the flaw could lead to remote code execution.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 07

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

A flaw in Telegram for Android, present in versions 8.6.2 through 12.10.3, allowed remote code execution when users answered voice calls. This vulnerability, if chained with other bugs, could lead to full phone control, and was fixed in version 12.10.4.