AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: Could Telegram’s Android Call Flaw Affect Your Next Step? on ThorstenMeyerAI.com

Before you orderOffer from Amazon

Get audio and creator gear delivered free with Prime

  • Fast, free delivery on millions of items
  • Prime Video, Amazon Music and more included
  • Member-only deals all year
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

TL;DR

NebuSec disclosed a Telegram for Android call-handling flaw on October 29, 2026, saying it could be combined with two other bugs to take control of a phone after the user answered a call. Telegram had released a fix in version 12.10.4 in September, but the full attack chain has not been publicly documented and NebuSec says it has seen no attacks. Users should update and limit who can call them while doing so.

Security startup NebuSec disclosed a flaw in Telegram for Android on October 29, saying an attacker could use it as part of a chain of bugs to take control of a phone after the user answered a call. Telegram had already fixed the reported call-code issue in version 12.10.4, released in September, but the full exploit chain has not been documented publicly and NebuSec says it has seen no real-world attacks.

NebuSec says the affected Android releases run from version 8.6.2 through 12.10.3, spanning March 2022 to September 2026. The company describes the flaw as a memory bug in Telegram’s voice-call code. According to NebuSec chief executive Eten Zou, the call bug alone was not enough: an attacker also needed a second bug to escape the Telegram app and a third Android exploit to gain root, or administrator-level, access.

The attack would require the target to answer an incoming call, making it a one-click scenario rather than an attack that works without user interaction. NebuSec says it tested the chain in private voice calls on ARM64 phones, a processor architecture used by most modern Android devices. Its short demonstration shows a call connecting before the victim phone returns to its home screen, but the video does not identify the Telegram or Android versions used.

The publicly available evidence is limited. NebuSec announced the issue on X and described it to The Hacker News, but its research page did not contain a technical write-up as of October 29. The source material reports that Telegram’s Android code is public and that a comparison of versions 12.10.3 and 12.10.4 shows a change to the handling of a call-status field. Telegram had acknowledged NebuSec’s report, Zou said, but reportedly did not consider the issue capable of remote code execution. No CVE number was assigned, and Zou said no bounty was paid.

At a glance
reportWhen: Disclosed October 29, 2026; Telegram’s…
The developmentSecurity startup NebuSec disclosed a Telegram for Android call flaw that it says could enable a multi-stage attack after a user answers, months after Telegram released a fix.
Thorsten Meyer AI
Case file

Infographic 01 · Telegram for Android

One tap on “answer”, three bugs, one fix.

What is confirmed, what rests on NebuSec’s word, and what nobody knows yet about the voice-call flaw fixed in Telegram for Android 12.10.4.

12.10.4Telegram for Android version with the fix (source published 24 Sep 2026)
~4.5 yrsvulnerable range per NebuSec: 8.6.2 (March 2022) to 12.10.3 (September 2026)
1 tapthe victim has to answer the call. Declining, or calls set to “Nobody”, blocks it
0CVE numbers assigned. No entry in CISA’s list of exploited bugs either
  1. The callAn ordinary Telegram account calls the victim
  2. The tapThe victim answers. Without this, no attack
  3. Bug 1Call code misreads a status message (MediaState)
  4. Bug 2An information leak helps break out of the app
  5. Bug 3An Android root exploit: messages, mic, camera

Chain as described by NebuSec’s CEO to The Hacker News. Bugs 2 and 3 are not public; no technical write-up exists yet.

Checked myself
  • The bug and the fix match in Telegram’s public source (12.10.3 vs 12.10.4)
  • Same correction in the shared call library on 21 Apr 2026, titled “Fix camera rotation”
  • No CVE in the US vulnerability database (29 Oct)
  • No Telegram entry in CISA’s exploited-bugs catalog (28 Oct)
NebuSec says
  • Three chained bugs give full control of the phone
  • Versions 8.6.2 to 12.10.3 are affected
  • Its GPT-5.4-based product found the bug
  • No real attacks seen; Telegram did not see code execution, paid no bounty
Not known
  • What bugs 2 and 3 are
  • Whether the chain works on fully patched Android
  • Whether the old iOS and desktop code was exploitable
  • Telegram’s own statement
  • Mar 2022Version 8.6.2First version NebuSec names as affected
  • 21 Apr 2026Shared call library fixedtgcalls change “Fix camera rotation”. iOS picks it up in May, desktop in July (per The Hacker News)
  • 24 Sep 2026Android 12.10.4 source published156 days after the library fix (my arithmetic)
  • 26 Sep 2026NebuSec reports to TelegramTelegram acknowledges, does not consider it code execution (per NebuSec)
  • 29 Oct 2026Public disclosurePost on X with a 22-second demo video

Sources: NebuSec on X, 29 Oct 2026; The Hacker News, 29 Oct 2026; Telegram Android source 12.10.3 vs 12.10.4; tgcalls, 21 Apr 2026; NVD search, 29 Oct 2026; CISA KEV 2026.10.28. Status labels and arithmetic: Thorsten Meyer.
Powered by Thorsten Meyer AI

Why Answered Calls Can Matter

The reported issue highlights a risk in a feature designed to receive data from someone outside a user’s contacts: incoming calls begin exchanging setup and status information as the app connects. A mistake in handling that data may matter even when a user does not open a file or tap a link. In this case, however, NebuSec says answering was required, and the reported takeover depended on additional vulnerabilities.

For individual users, the immediate action is straightforward: check Telegram’s version and install 12.10.4 or a later release. Until updated, the source recommends changing “Who can call me?” to My Contacts or Nobody and declining calls from unknown callers. Those steps reduce exposure to this described call-based route; they do not establish that all possible attack paths are blocked.

The lack of a CVE also has implications for organizations. Security systems that track vulnerabilities only through CVE identifiers may not flag this report. Companies managing work phones may need to set minimum app versions and establish rules for messaging applications rather than relying solely on public vulnerability databases.

Products Worth Considering

Apple AirPods Pro (2nd Generation) Wireless Earbuds with USB-C MagSafe Charging Case

Apple AirPods Pro (2nd Generation) Wireless Earbuds with USB-C MagSafe Charging Case

Bose QuietComfort True Wireless Earbuds with Active Noise Cancellation, Bluetooth 5.3, USB-C Charging, IPX4, Black

Bose QuietComfort True Wireless Earbuds with Active Noise Cancellation, Bluetooth 5.3, USB-C Charging, IPX4, Black

Logitech MX Mechanical Wireless Illuminated Keyboard, Tactile Quiet, Graphite

Logitech MX Mechanical Wireless Illuminated Keyboard, Tactile Quiet, Graphite

As an affiliate, we earn on qualifying purchases.

The September Code Change

Telegram released Android version 12.10.4 in September, before NebuSec’s October 29 public disclosure. The source material says the fix can be seen by comparing the Android call code in versions 12.10.3 and 12.10.4: the older code checked that a camera-rotation value existed but then read a different field, while the newer code reads the rotation field. This is a description of the code change, not proof on its own that the entire attack chain worked as described.

The correction also appeared earlier in Telegram’s shared call library, tgcalls, according to the source, in an April 21, 2026 change titled “Fix camera rotation.” The same material says iOS and desktop versions later incorporated the change, but it does not establish that those versions were exploitable. NebuSec reported the flaw to Telegram on September 26, after the fixed Android release had appeared.

As of October 29, the US National Vulnerability Database had no CVE listing for the flaw, and the CISA catalog of known exploited vulnerabilities contained no Telegram entry. Those absences mean there was no listing in those sources at that time; they do not confirm that no attack occurred.

“Now picking up a wrong call can get you hacked.”

— NebuSec, in its October 29 post on X

What the Public Evidence Leaves Open

The full chain remains unverified in a public technical report. The source material says the second information-leak bug and the Android root exploit could not be checked independently. It is also unclear whether the chain works on a fully patched Android phone, whether anyone used it before disclosure, or which exact operating-system and app versions appear in NebuSec’s demonstration.

NebuSec says it has seen no real attacks, but that is not proof that none occurred. The source reports no public response from Telegram as of October 29. It also says NebuSec found no evidence that group calls, iOS, or desktop apps were directly affected; that should not be read as confirmation that every version or configuration of those apps is safe.

Update and Watch for Details

Android users should check Telegram’s version in Settings and update to 12.10.4 or later if needed. People who cannot update immediately can restrict incoming calls to contacts or turn them off, and should avoid answering unexpected calls while the app is outdated.

Further clarity depends on a fuller technical account from NebuSec or a response from Telegram. Such details could establish the Android versions and conditions needed for the complete chain, and clarify whether the other reported bugs were fixed separately. Organizations should check app-version compliance on managed phones and avoid treating the absence of a CVE as evidence that no action is needed.

Key Questions

What is the reported Telegram flaw?

NebuSec describes a memory bug in Telegram’s Android voice-call code. The company says it could be combined with two other bugs to gain control of a phone after the user answered a call.

Which Telegram Android versions are named as affected?

NebuSec identifies versions 8.6.2 through 12.10.3 as affected and says the issue was fixed in version 12.10.4. The complete exploit chain has not been publicly documented.

Does answering a call alone give an attacker control?

Not according to NebuSec’s account. It says the call flaw had to be combined with two additional bugs, including an Android root exploit. The target also had to answer, so the described attack is not zero-click.

What should Telegram users do now?

Update Telegram for Android to version 12.10.4 or later. If an update is not immediately available, restrict “Who can call me?” to My Contacts or Nobody and decline unexpected calls.

Is there evidence that attackers used the flaw?

NebuSec says it has seen no real-world attacks. The source material also reports no CVE listing as of October 29, 2026. These facts do not prove that exploitation never occurred.

Source: ThorstenMeyerAI.com

You May Also Like

RHEO on the Web: Find Your Flow

Discover RHEO’s web version—an instant, private browser-based fluid simulation for relaxation, breathing, and creative experimentation, accessible without downloads.

Show HN: Guitoro, A Virtual Guitar You Strum With Your Keyboard

Guitoro is a browser-based virtual guitar played with a keyboard, touchscreen or mouse, with recorded instrument sounds and song playback tools.

Can Learning AI Help Young People Navigate The UK Jobs Market?

Youth unemployment reached 15.6% in summer 2026 as AI mentions in job ads rose. The data do not show AI caused the jobs squeeze.

How AI And CCTV Improve Near-Miss Detection In Industrial Environments

New AI-powered system uses existing CCTV to identify near-misses, improving safety and reducing injuries in industrial warehouses.