Key Highlights:
- Security researchers revealed that older Telegram versions could execute code via bot-delivered HTML and JavaScript widgets when rendering chat messages without requiring an active tap.
- Telegram founder Pavel Durov maintained that users must first interact with a third-party service and stated that the vulnerability has been mitigated on the server side.
- Cryptocurrency exchange Bybit urged users to update their Telegram apps immediately, though no customer asset losses or full-device root exploits have been reported.
Analysis of the Telegram Bot Widget Vulnerability
Recent disclosures surrounding Telegram’s messaging architecture have brought scrutiny to the platform’s developer interfaces and client-side security. The controversy stems from capabilities introduced around Bot API 10.4, detailed in Telegram’s official BotNews channel, which allowed developers to run interactive HTML interfaces directly within chat message bubbles. These tools were designed to streamline in-app functionality, featuring TON wallet integrations for signing transactions, notifying bots of on-chain activities, and inspecting wallet cards and account balances. While these developer features established complex in-chat payment pathways, technical documentation shows that their inclusion alone does not constitute evidence of unauthorized asset transfers.
Technical details emerged from an archive compiled by security researchers titled tg-widget-rce, which outlines how a malicious payload could trigger execution. According to the researchers, a bot permitted to distribute widgets could dispatch a message carrying HTML and JavaScript. When Telegram rendered and laid out the message within an open chat window, the widget executed automatically without demanding a manual tap from the recipient. This dynamic highlighted a technical divergence: while engaging with a bot service requires an initial opt-in, rendering an incoming widget inside an established conversation occurred passively.
Dissecting the ‘No Tap’ Execution and Client Versions
Telegram founder Pavel Durov addressed the security reports on Nov. 13, pushing back against claims of passive compromise. Durov emphasized that users could not be compromised simply by receiving an unsolicited message, asserting that a user had to deliberately initiate a third-party service beforehand. “Even that is fully patched server-side,” he wrote, underscoring that infrastructure-level safeguards had been deployed to block improper widget transmissions.
The research documentation identifies several older software releases as vulnerable prior to recent patches. The affected clients listed in the archive include Telegram for Android version 13.2.0, Telegram for iOS version 13.2, Telegram Desktop version 7.4.0, and Telegram for macOS version 13.1. Security analysts confirmed that these specific vulnerabilities have been resolved in current application builds. Furthermore, granular testing across Android builds revealed varying levels of containment: older builds 72889 and 72929 permitted code execution directly within the core Telegram application space, whereas subsequent builds 72979 and 72989 confined the execution to an isolated widget process. Crucially, the researchers did not claim root, kernel, or bootloader-level privileges, indicating the flaw did not confer total operating system control.
Exchange Advisories and Multi-Layered Remediation
The technical findings prompted immediate advisories across the digital asset sector. Cryptocurrency exchange Bybit issued a warning to its user base on Nov. 13, advising account holders to immediately update Telegram across all desktop and mobile devices. Bybit also instructed users to avoid interacting with unfamiliar bots, steer clear of unrecognized chat groups, and refrain from clicking unverified links. The exchange noted that an app-level compromise could potentially expose other device functions to risk, though the advisory was explicitly framed as a protective recommendation rather than an announcement of direct customer financial losses.
For end users operating outdated software, security analysts emphasize the interplay between server defenses and client patches. Restricting delivery protocols on Telegram’s central servers prevents bots from dispatching dangerous widgets, but client-side updates are necessary to eliminate the underlying rendering vulnerabilities in the code itself. While server-side mitigations disrupt known attack routes, neither server filters nor public statements provide an exhaustive matrix of safe legacy builds, making rapid client software updates the primary line of defense.
Why This Matters
The incident highlights the growing security risks associated with turning messaging applications into expansive application ecosystems. By embedding web execution engines, HTML widgets, and integrated cryptocurrency wallets like TON directly into chat interfaces, modern messaging platforms increasingly face threats typically associated with full web browsers. While server-side fixes allow platforms like Telegram to rapidly neutralize exploits centrally without waiting for user action, legacy software clients that retain unpatched code remain structurally vulnerable until updated, underscoring the vital need for prompt client-side patch management in apps handling financial interactions.
Frequently Asked Questions
Can a Telegram user be compromised simply by receiving a text message?
According to Pavel Durov, users cannot be compromised merely by receiving a standard message, as interacting with a third-party bot service is required first, and server-side patches have been deployed. However, researchers noted that once a permitted bot sent a malicious widget into an active chat, older client versions executed the embedded code during message layout without requiring a tap on the widget itself.
Which Telegram versions were identified as vulnerable?
The researchers’ archive lists older client releases, specifically Telegram for Android 13.2.0, Telegram for iOS 13.2, Telegram Desktop 7.4.0, and Telegram for macOS 13.1. These vulnerabilities are reported to be fixed in current, up-to-date versions of the application.
Were cryptocurrency balances or full devices compromised?
The research findings do not document root, kernel, or full-device takeovers, nor is there evidence of unauthorized asset transfers or customer losses. The advisory issued by cryptocurrency exchange Bybit was a precautionary measure reminding users to update their software rather than a report of an active financial breach.




