Threat intel4 min read
Telegram blocks bot widgets after code-execution claims on Android
Four days after launching HTML widgets, Telegram stopped most bots from sending them. Its Android sandbox ships with the seccomp filter in audit mode, and new bypass claims remain unconfirmed.
4Tify Team

Telegram has stopped most bots from sending its new HTML widgets, four days after launching them, while code-execution claims against the Android app pile up. No CVE has been assigned, there is no vendor advisory, and some of the claims remain unverified.
What happened
Widgets arrived with Bot API 10.4 on 9 November 2026. A bot can now send a message that carries a small HTML document with its own JavaScript, and the recipient's app runs it inside the chat. Telegram's Bot API changelog limited them to private chats in production from day one.
On 11 November a video appeared showing a bot interaction that opened the Calculator app on an Android phone, the classic way to show that outside code is running on a device. Telegram said the Android problem was fixed on 10 November and that the fix reached all users the following day.
On 13 November Telegram's chief executive, Pavel Durov, said no one could be hacked just by receiving a message. In his account, an attack needed the user to start a third-party service first, and that path was fully patched on the server side. The same day, bots that had been sending widgets started getting the error INPUT_MEDIA_WIDGET_NOT_ALLOWED. A Telegram Bot API maintainer confirmed on GitHub that general bots are currently not allowed to use widgets, even in private chats. On 17 November the same maintainer said widgets are not enabled for Premium users either.
The Android hardening, and its limits
The Android code Telegram published for version 13.2.2 (7303) on 12 November shows how the app now contains widget code:
- widget JavaScript runs in QuickJS, a small JavaScript engine, inside a separate isolated Android process with no permissions, files or network access;
- a single process runs every widget, so widgets from different bots share it;
- a seccomp filter limits which Linux system calls that process may make, aimed at ptrace, eBPF, mount and similar kernel features;
ioctlis deliberately left unfiltered.
The filter also ships switched to audit mode. In the published code the enforce flag is set to false. In that mode the process still cannot start new programs, but the other listed calls are only logged and allowed through. A code comment says audit mode stays until device logs show the engine never makes those calls. It is not known whether the build users install from app stores uses the same setting.
Claims that are not yet confirmed
A second security team says it found two ways out of that filter on 13.2.2 (7303). One relies on a widget bug the filter does not cover, the other chains a covered widget bug with an Android kernel bug. The demonstration ran on a Telegram test server, because live bots can no longer send widgets. No CVE, fixed version or full technical details have been published, and it is not clear what the code could reach beyond the widget process.
A separate video claims a working exploit against the Windows desktop app after the Android fix. That has not been independently confirmed either.
There is also suspected abuse in the wild. An antivirus vendor detected attempts from the night of 13 November in which visiting certain Telegram channels launched a hidden PowerShell script. The script downloaded WebRAT, also known as Salat Stealer, a Rust-based trojan that gives attackers remote control and steals crypto wallet and Telegram account data. No victim count, client version or technical detail was disclosed, and the link to widgets has not been confirmed.
Who is affected
Anyone running a Telegram client that renders HTML widgets. The code-execution demonstrations target Android, plus Windows in the unconfirmed second video. Telegram has not said whether other platforms were affected. With bots blocked from sending widgets on the server, the immediate exposure is low. That changes the moment Telegram switches them back on.
What to do now
- Update Telegram on every device to the latest version from the official store or telegram.org. On Android, check Settings, where the version is shown at the bottom.
- Do not open or interact with widgets from bots you do not know, and be wary of unfamiliar channels pushing interactive content.
- On Windows machines, watch for PowerShell launched by the Telegram desktop process. Endpoint tools can alert on that parent and child pair.
- If Telegram is used for work, treat it like any other managed app: track installed versions centrally and decide whether widgets are acceptable before they return.
- Follow Telegram's own channels for the date widgets come back and for any change to the Android seccomp mode.
Knowing which version of an app is actually running across a fleet is where most patching plans fall apart. Our vulnerability scanning service flags outdated and exposed software across your estate, so a client update like this one does not slip past unnoticed.