CVE-2026-109426

Telegram-Stremio 5.1.0 Insecure Session Storage via encode_string

Published Oct 12, 2026 CVSS 4.0 · 8.2 High EPSS < 1% KEV · Not listed
Description
Telegram-Stremio through 5.1.0 contains an insecure storage vulnerability that allows attackers with access to the MongoDB database, backups, or logs to recover the operator's authenticated Telegram session string, which is protected only by a keyless, reversible encoding transform rather than actual encryption. Attackers can round-trip the stored value through the repository's own decode_string function with no secret key to obtain a fully authenticated Telegram session, granting complete control of the operator's Telegram account even when two-step verification is enabled.

Analysis

AI-generated

Technical impact

Telegram-Stremio versions up to 5.1.0 store the operator’s Telegram session string in a MongoDB database using a reversible encoding function without a secret key. An attacker who can read the database, backups, or logs can decode the stored value and obtain a fully authenticated Telegram session, thereby taking complete control of the operator’s Telegram account even when two‑step verification is enabled. The vulnerability is a classic example of improper cryptographic handling (CWE‑312).

Affected Systems

The affected product is Weebzone’s Telegram‑Stremio, specifically version 5.1.0. The vendor product pairing is Weebzone:Telegram‑Stremio, and all installations of this version are impacted unless mitigated by configuration changes.

Risk and Exploitability

The CVSS score of 8.2 indicates a high severity risk. EPSS data is not available, and the vulnerability is not listed in CISA’s KEV catalog, so the exploit probability is uncertain but potentially significant for systems with exposed database access. The likely attack vector requires the attacker to have database or backup access; once that is obtained, the session token can be recovered with no additional secret. Successful exploitation leads to full control of the operator’s Telegram account, presenting a critical threat to communications and potential downstream systems.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Telegram‑Stremio to a patched version that encrypts or removes the insecure session storage feature.
  • If an upgrade is not yet available, delete or obfuscate any stored session strings in the MongoDB database and any backup files to prevent future decoding.
  • Revoke all existing Telegram session tokens used by the operator, generate new session credentials, and update the application configuration accordingly.
  • Restrict database and backup access by implementing network segmentation and strong authentication controls to limit exposure to potential attackers.

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

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', '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 an insecure storage vulnerability that allows attackers with access to the MongoDB database, backups, or logs to recover the operator's authenticated Telegram session string, which is protected only by a keyless, reversible encoding transform rather than actual encryption. Attackers can round-trip the stored value through the repository's own decode_string function with no secret key to obtain a fully authenticated Telegram session, granting complete control of the operator's Telegram account even when two-step verification is enabled.
Title Telegram-Stremio 5.1.0 Insecure Session Storage via encode_string
Weaknesses CWE-312
References
Metrics cvssV3_1

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

cvssV4_0

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

Weaknesses
  • CWE-312

    Cleartext Storage of Sensitive Information

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 13, 2026, 3:54 PM
Reserved
Oct 12, 2026, 3:52 PM
Status
Deferred
Published
Oct 12, 2026, 9:17 PM
Modified
Oct 16, 2026, 7:18 PM