CVE-2026-109426Telegram-Stremio 5.1.0 Insecure Session Storage via encode_string
Updated under an hour ago ()
Does this affect you?
It affects weebzone Telegram-Stremio. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.11%, higher than 1% of scored CVEs.
Do this next
Free account, 1 product
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.
- CVSS
- 7.5 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Weakness (CWE)
- CWE-312
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.11% (percentile 1)
- Assigned by
- VulnCheck
- NVD analysis
- Deferred
- Record last updated
- Oct 13, 2026
- First seen by InfoSec Signals
- Oct 12, 2026
Affected products
weebzone Telegram-Stremio weebzone:telegram_stremio (from the name) | through 5.1.0 | CNA record |
References
- https://gist.github.com/mansurmavlankulov/489554cad7b38e07b9651c217f00fffbtechnical-description
- https://www.vulncheck.com/advisories/telegram-stremio-insecure-session-storage-via-encode-stringthird-party-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.