Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Tue, 13 Oct 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 13 Oct 2026 07:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Weebzone
Weebzone telegram-stremio |
|
| Vendors & Products |
Weebzone
Weebzone telegram-stremio |
Mon, 12 Oct 2026 20:45:00 +0000
| 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
|
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-10-13T15:54:08.333Z
Reserved: 2026-10-12T15:52:36.681Z
Link: CVE-2026-109426
Updated: 2026-10-13T15:54:03.874Z
Status : Received
Published: 2026-10-12T21:17:11.310
Modified: 2026-10-13T16:17:17.557
Link: CVE-2026-109426
No data.
OpenCVE Enrichment
Updated: 2026-10-13T07:25:41Z