NewsCryptoTelegram Blocks Bot Widgets as Researchers Detail Security Flaws in Older Clients

Telegram Blocks Bot Widgets as Researchers Detail Security Flaws in Older Clients

Author: CryptoNewsNet·

Key Takeaways

  • •Telegram stopped allowing general bots to send HTML widgets even in private chats, a restriction confirmed on Nov. 13 by Bot API repository contributor Aliaksei Levin.
  • •CEO Pavel Durov stated the security issue was fully patched server-side and that no one could be hacked simply by receiving a message.
  • •Security researchers documented a trigger in which a widget carrying HTML and JavaScript executed when Telegram laid out the message in an open chat, with no tap required.
  • •The flaws affected older clients including Telegram for Android 13.2.0, iOS 13.2, Desktop 7.4.0 and macOS 13.1, and are fixed in current Telegram builds, with no root, kernel or bootloader exploit claimed.
  • •Crypto exchange Bybit urged users on Nov. 13 to update Telegram immediately, avoid unfamiliar chats and unknown bots, and refrain from opening suspicious links.
Telegram Blocks Bot Widgets as Researchers Detail Security Flaws in Older Clients

Telegram Blocks Bot Widgets as Researchers Detail Security Flaws in Older Clients

Telegram has barred general bots from sending HTML widgets — interactive tools that run inside messages — after security researchers detailed flaws in older clients and Telegram CEO Pavel Durov said the underlying issue had been patched server-side.

“Yes, currently, general bots aren't allowed to use widgets even in private chats,” Aliaksei Levin, a contributor to the Bot API repository posting as levlam, wrote on Nov. 13.

Levin was responding to a developer who reported that a bot that had successfully delivered widgets from Nov. 10 through part of Nov. 13 was suddenly receiving a permission error. The confirmation covers widget sending only. It does not amount to a freeze on bot registration or a blanket shutdown of Telegram Mini Apps, and it does not clarify whether previously delivered widgets still render, why access was narrowed, or when it might be restored. For developers and the users who interact with their bots, the immediate practical effect is that widget-based interfaces can stop delivering even in one-on-one conversations.

A New Interface for In-Chat Payments

The restriction closes off a newly introduced interface for developers building tools and payment flows inside chats. Telegram's official BotNews announcement for Bot API 10.4 described HTML interfaces running directly inside message bubbles, alongside TON wallet integration covering transaction signing, transaction notifications for bots, and the ability to read wallet cards, including balances. Those capabilities are not, in themselves, evidence that a security flaw enabled unauthorized transfers.

What the "No Tap" Trigger Means

Durov said on Nov. 13 that nobody could be hacked simply by receiving a message, noting that users first had to actively start a third-party service. “Even that is fully patched server-side,” he wrote.

The researchers' tg-widget-rce archive, however, describes a more specific trigger: a bot message carrying HTML and JavaScript, with the widget executing when Telegram lays out the message in an open chat — no tap required. Delivery still depends on a bot being permitted to send widgets, and starting a service and tapping an individual widget remain separate actions.

According to the archive, the affected older versions include Telegram for Android 13.2.0, Telegram for iOS 13.2, Telegram Desktop 7.4.0 and Telegram for macOS 13.1. The researchers say the published flaws are fixed in current Telegram builds.

Their build-specific findings distinguish code execution inside the Telegram app on older Android builds 72889 and 72929 from results contained within an isolated widget process on builds 72979 and 72989. The researchers do not claim a root, kernel or bootloader exploit, so the findings should not be read as proof of full-device control.

The distinction matters for users who have not updated: patching client code and restricting delivery on Telegram's servers address different parts of the attack path. The two fixes also reach devices differently — a server-side gate applies to chats the moment it is active, regardless of which app version a person is running, while client-side patches protect a device only once its updated build is installed. The archived tests do not establish that older clients remain exploitable under the current server rules, and Durov's statement does not provide a minimum safe version for every client.

Crypto exchange Bybit urged users on Nov. 13 to update Telegram immediately, avoid unfamiliar chats and unknown bots, and refrain from opening suspicious links. Its warning that a compromised device could put other apps at risk was framed as an advisory, not a report of customer losses.