Lucene search
+L

4 matches found

CVE
CVE
•added 2026/10/12 8:35 p.m.•6 views

CVE-2026-109427

Telegram-Stremio versions through 5.1.0 are affected by a broken object-level authorization vulnerability. The root cause is the use of encode_string and decode_string functions to process unsigned, unauthenticated stream IDs. Authenticated token holders can exploit this by crafting or enumeratin...

7.1CVSS6AI score
SaveExploits0References2
Cvelist
Cvelist
•added 2026/10/12 8:35 p.m.•13 views

CVE-2026-109427 Telegram-Stremio 5.1.0 Broken Object Authorization via Stream IDs

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 encodestring/decodestring functions. Attackers can craft or enumerate...

7.1CVSS
SaveExploits0References2
CVE
CVE
•added 2026/10/12 8:34 p.m.•6 views

CVE-2026-109426

Telegram-Stremio versions through 5.1.0 are vulnerable to an insecure storage flaw. The application fails to properly encrypt authenticated Telegram session strings, instead using a keyless, reversible encoding transform. Attackers who gain access to the MongoDB database , backups , or logs can u...

8.2CVSS5.9AI score
SaveExploits0References2
Cvelist
Cvelist
•added 2026/10/12 8:34 p.m.•14 views

CVE-2026-109426 Telegram-Stremio 5.1.0 Insecure Session Storage via encode_string

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...

8.2CVSS
SaveExploits0References2
Rows per page
Query Builder