Security researchers at NebuSec say they identified two methods for escaping security controls recently added to Telegram's Android widget environment. The claims concern interactive bot widgets, which run JavaScript through the QuickJS engine when used in Telegram chats.
Telegram introduced additional protections after public reports alleged that malicious messages could trigger remote code execution. The company separated the QuickJS runtime into its own Android process and applied a seccomp policy intended to limit dangerous system calls. Telegram CEO Pavel Durov has said users could not be compromised merely by receiving a message and that use of third-party services was required in the previously reported scenario.
Claims remain limited and unverified
NebuSec said it demonstrated code execution outside the new seccomp restrictions on Telegram for Android version 13.2.2 (7303), using a test server. In a video, the researchers showed a widget opening Android's calculator application. They did not publish technical proof-of-concept code, identify CVEs, or specify whether the issues were disclosed to Telegram before publication.
According to the researchers, one proposed route relies on a widget-engine vulnerability not addressed by the filter, while another combines an engine flaw with a kernel issue. The available information does not establish the practical impact of either method, including whether an attacker could access Telegram messages, device data, or other applications. It also remains unclear what user interaction would be needed before a malicious widget could execute.
Sandbox design and deployment questions
The analysis argues that a memory-safety flaw in QuickJS, such as a use-after-free or out-of-bounds write, could undermine restrictions implemented inside the JavaScript engine. NebuSec also noted that the published filter allows many system calls and does not restrict ioctl.
Researchers further observed that Telegram's published Android source appeared to configure some seccomp rules for audit mode, which logs selected calls rather than blocking them. The source code alone does not confirm that the same policy is active in the production application distributed to users.
Telegram has restricted general bots from using widgets, including in private chats, according to comments in a public bot API issue thread. The scope and duration of that restriction were not clear at the time of reporting.
Separately, Kaspersky reported suspected exploitation involving Telegram widgets and a PowerShell-delivered remote-access tool, but did not link that activity to NebuSec's research or identify the underlying Telegram flaw. Users should keep Telegram and Android updated, avoid launching untrusted bot services or widgets, and monitor official vendor advisories for confirmed fixes.
