← News

Researchers point out that exploitation of widgets in Telegram Android allows remote code execution

NebuSec researchers revealed two vulnerabilities that allow widgets sent by bots in Telegram Android to bypass the seccomp filter and execute code outside the application's process.

By CyberX I.T SolutionsCibersegurança6 min readSource: Researchers Claim Two RCE Exploits That Bypass Telegram’s New Android Defenses ↗Ler em português →

A malicious widget can bypass Telegram's new security protection for Android and execute code outside the application process.

Researchers at NebuSec demonstrated that two distinct vulnerabilities allow a bot‑delivered widget to run arbitrary code on an Android device, even after the update that introduced the seccomp filter and the execution of the QuickJS engine in an isolated process.

Widgets are interactive blocks that bots can embed in messages. The JavaScript of these widgets runs on the user's phone. In November 2026, Telegram began allowing bots to send widgets, but also introduced two hardening measures: it moved the QuickJS engine to its own process and added a seccomp filter that logs or blocks specific system calls.

The first vulnerability exploited by the researchers resides in a bug in the widget itself that the seccomp filter does not cover. It is a use‑after‑free or out‑of‑bounds write in the QuickJS engine, which allows the widget script to read and write the process memory, bypassing sandbox restrictions.

The second exploit chain combines the same widget bug with an Android kernel vulnerability that enables privilege escalation. The seccomp filter blocks some critical calls but leaves the ioctl call unrestricted, which an attacker can use to interact with the vulnerable kernel and gain full control.

In the demonstration recorded by the researchers, the compromised widget opens the phone's calculator app, proving that the code can run outside the QuickJS sandbox. The video does not reveal whether the code could access messages, files, or other device resources.

The NebuSec report did not receive a CVE identifier and does not indicate whether the flaws were reported to Telegram. The source code published by Telegram for Android 13.2.2 (7303) shows that the seccomp filter is set to “audit” mode, logging unlisted calls but allowing their execution. The filter still leaves the ioctl call unfiltered.

Furthermore, Telegram limited widget usage to approved bots; generic bots still cannot send widgets in private chats. A contributor to the telegram‑bot‑api project confirmed this restriction at the end of November 2026.

Pavel Durov, Telegram’s CEO, stated that no user could be compromised merely by receiving a message, and that the demonstrated vulnerability required the user to interact with a third‑party service, which has already been fixed on the server side.

Separately, Kaspersky disclosed that it detected suspicious activity related to Telegram widgets, including a PowerShell script that downloaded and executed the WebRAT malware (also known as Salat Stealer). The advisory does not link the activity to a specific app version nor quantify victims.

While Telegram has not yet released an update that fully disables widgets or fixes the QuickJS bug, it is recommended that organizations disable the widget feature on corporate devices, monitor system‑call logs related to ioctl, and keep Android and Telegram up to date. The security community will continue to monitor possible field exploitation reports.

Technical Analysis CyberX

NebuSec identified two distinct exploitation paths that bypass the defenses introduced by Telegram for Android 13.2.2.

Bug in the QuickJS Engine

The QuickJS JavaScript engine, responsible for executing widget code, was moved to a dedicated process. However, a use‑after‑free or out‑of‑bounds write error allows a script to corrupt the process memory, overwriting sandbox control structures. When memory is corrupted, the permission checks implemented in the engine are bypassed, allowing the widget to invoke Android APIs that would normally be blocked.

Incomplete seccomp filter

The seccomp filter implemented by Telegram lists dozens of system calls (e.g., ptrace, bpf, mount) and blocks or logs those calls. However, the ioctl call remains unfiltered, creating an attack surface. An attacker can use ioctl to interact with vulnerable kernel drivers, enabling privilege escalation when combined with the QuickJS memory corruption.

Combined exploitation chain

The second path combines the QuickJS bug with a known Android kernel vulnerability (not publicly disclosed) that can be triggered via ioctl. This chain allows the widget code to escape the QuickJS process sandbox and execute code in the kernel context, potentially granting the attacker full control.

Potential Impact

  • Confidentiality: access to messages, stored credentials, and user files.
  • Integrity: possibility to inject or modify data in installed applications.
  • Availability: execution of code that could install backdoors or ransomware.

Demonstration limitations

The presented proof of concept only opens the calculator app, without demonstrating access to sensitive data or persistence. There is no information about the need for user interaction (e.g., tapping the widget) before execution.

Defensive Recommendations

  • Disable the widget feature on corporate devices until Telegram releases a definitive fix.
  • Apply restrictive SELinux policies that limit ioctl calls from unprivileged processes.
  • Monitor seccomp audit logs to identify unexpected ioctl calls.
  • Keep Android and Telegram up to date; verify the presence of security patches released after 13.2.2.
  • Implement EDR solutions that detect anomalous widget process behavior, such as attempts to launch external applications.

CyberX SOC Intelligence Bulletin

Telegram Android 13.2.2 (7303) contains two vulnerabilities that allow remote code execution via widgets, bypassing the seccomp filter and exploiting a bug in the QuickJS engine.

Assets and exposure conditions

Devices running version 13.2.2 or later of Telegram for Android with widgets enabled are potential targets. Approved bots that can send widgets increase the risk surface.

Investigation indicators

  • Seccomp audit‑mode logs that record unexpected ioctl calls.
  • Events of child‑process creation from the QuickJS process.
  • Execution of unsolicited applications (e.g., calculator) launched by widget processes.

Indicators of Compromise (IoCs)

So far, no hashes of malicious binaries, IP addresses, or domains associated with active exploitation have been disclosed. The absence of verifiable IoCs was confirmed in the consulted sources.

MITRE ATT&CK

  • T1059 – Command and Scripting Interpreter (use of JavaScript in the widget).
  • T1203 – Exploitation for Client Execution (exploit of a bug in QuickJS).
  • T1068 – Exploitation for Privilege Escalation (use of ioctl to elevate privileges via the kernel).

Fixes and Mitigation

  • Update Telegram to the version that removes or fixes the QuickJS bug (when available).
  • Disable widgets via mobile device management (MDM) policy until the fix is released.
  • Apply custom seccomp rules that block ioctl for widget processes.
  • Strengthen monitoring of suspicious system calls with EDR/SIEM.

Response and Evidence Preservation

In case of suspected exploitation, isolate the device, collect seccomp logs and QuickJS process logs, and preserve volatile memory for forensic analysis. Notify the vendor (Telegram) and, if applicable, the national CERT.

Frequently Asked Questions

What are the two vulnerabilities discovered by NebuSec?

A use‑after‑free/out‑of‑bounds write in QuickJS and a chain with an Android kernel ioctl vulnerability.

How does the widget bypass the seccomp filter?

The QuickJS bug corrupts memory, allowing the widget to read/write process memory, and the ioctl call is left unfiltered, enabling kernel interaction.

Has Telegram released a patch for these issues?

Telegram has not yet released an update that fully disables widgets or fixes the QuickJS bug.

What should organizations do to protect their devices?

Disable the widget feature on corporate devices, monitor ioctl system‑call logs, and keep Android and Telegram up to date.

Are there known active exploits or IoCs?

No hashes, IPs, or domains associated with active exploitation have been disclosed.

Esta análise foi útil?

Ainda não há avaliações.