CVE-2026-109427

Telegram-Stremio 5.1.0 Broken Object Authorization via Stream IDs

Published Oct 12, 2026 CVSS 4.0 · 7.1 High EPSS < 1% KEV · Not listed
Description
Telegram-Stremio through 5.1.0 contains a broken object-level authorization vulnerability that allows authenticated token holders to access arbitrary chat messages by forging unsigned, unauthenticated stream IDs decoded via encode_string/decode_string functions. Attackers can craft or enumerate sequential msg_id values and set a global flag in the stream_handler endpoint to route requests through the operator's personal Userbot account, exposing private channels, groups, and Saved Messages, while the unauthenticated thumb_handler endpoint further discloses thumbnails from those same chats without any token validation.

Analysis

AI-generated

Technical impact

Telegram-Stremio 5.1.0 contains a broken object-level authorization flaw that lets authenticated users craft or enumerate stream IDs to read arbitrary messages from private channels, groups, and Saved Messages. The vulnerability is tied to the encode_string/decode_string functions and the stream_handler endpoint, which mistakenly allows a forged, unsigned stream ID to be routed through the operator’s personal Userbot account. Additionally, the thumb_handler endpoint exposes thumbnails from the same chats without requiring a token, further leaking private content. The impact is direct data leakage of user‐generated content and private communications.

Affected Systems

The affected product is Telegram-Stremio by weebzone, up to and including version 5.1.0. No other variants data were listed, so any deployment of this version is potentially vulnerable.

Risk and Exploitability

The CVSS score of 7.1 indicates a high-level impact. EPSS data is not available, and the vulnerability is not yet listed in CISA KEV. Based on the description, the likely attack vector involves a legitimate user account that can directly use known API endpoints; the attacker can craft sequential message IDs or use enumeration to locate sensitive content. The absence of authentication on thumb_handler makes that endpoint trivial to abuse, while the stream_handler misuse requires only crafting a stream ID. The overall risk is that any authenticated user can access private data and that unauthenticated users can view thumbnails, especially if the application is exposed on a public network.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Check Telegram-Stremio vendor advisories or official website for patch updates.
  • Disable or restrict access to the stream_handler and thumb_handler endpoints, ensuring only authenticated requests are allowed.
  • Monitor stream ID usage, block or rate‑limit enumeration attempts, and log any unauthorized accesses.

Generated by OpenCVE AI on October 12, 2026 at 21:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Weebzone
Weebzone telegram-stremio
Vendors & Products Weebzone
Weebzone telegram-stremio
Type Values Removed Values Added
Description Telegram-Stremio through 5.1.0 contains a broken object-level authorization vulnerability that allows authenticated token holders to access arbitrary chat messages by forging unsigned, unauthenticated stream IDs decoded via encode_string/decode_string functions. Attackers can craft or enumerate sequential msg_id values and set a global flag in the stream_handler endpoint to route requests through the operator's personal Userbot account, exposing private channels, groups, and Saved Messages, while the unauthenticated thumb_handler endpoint further discloses thumbnails from those same chats without any token validation.
Title Telegram-Stremio 5.1.0 Broken Object Authorization via Stream IDs
Weaknesses CWE-639
CWE-862
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

  • CWE-862

    Missing Authorization

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 26, 2026, 8:33 PM
Reserved
Oct 12, 2026, 3:52 PM
Status
Deferred
Published
Oct 12, 2026, 9:17 PM
Modified
Oct 26, 2026, 9:17 PM