Researchers Say Telegram's New Android Widget Sandbox Can Be Bypassed with Two RCE Chains
Security firm NebuSec says it has demonstrated two remote code execution (RCE) exploits that bypass a security filter Telegram added to its Android app last week to contain bot-supplied widgets. Widgets are small interactive JavaScript blocks that bots can send inside chat messages, and that script normally runs on the recipient's phone inside a restricted environment. According to the report, NebuSec's exploits let that code escape the filter and execute outside the intended sandbox. The demonstration was run on a Telegram test server, because sending widgets in production requires an approved bot account. The claims have not been shown to work against the live, public Telegram app.
Why It Matters
If the findings hold up against the production app, this would undermine a defense Telegram shipped to limit what bot-delivered widget code can do on a user's device. Telegram's Android user base is large. Any RCE-class bypass of a bot-content sandbox is significant. It would mean a malicious or compromised bot could run code on a victim's phone by sending a crafted widget, without further user action beyond viewing the message. At this stage, treat this as a researcher claim pending vendor confirmation and a production-environment proof, not a confirmed in-the-wild threat.
What Defenders Should Watch For
- Monitor for Telegram client updates or advisories addressing the widget security filter, and apply them promptly once available.
- For managed or enterprise Android fleets, consider whether Telegram bot interactions can be restricted or whether EMM/MDM policy can limit which apps can process untrusted bot content.
- Watch endpoint telemetry for anomalous process spawning, privilege changes, or network connections originating from the Telegram app shortly after receiving messages from bots, especially unfamiliar or newly added bots.
- Educate users on the risk of interacting with or adding bots from unverified sources, since widget delivery requires an approved bot in the chat.
This is a developing story based on a single vendor's claims, run against a test server rather than production Telegram. No CVE identifier has been referenced in the reporting. We will revisit this item as more technical detail or an official Telegram response emerges. Read the original coverage at The Hacker News.