Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
fast-mcp-telegram before 0.19.1 accepts a crafted Bearer token that uses path traversal to bypass the reserved-name check. A remote client without a valid token can then act as the default Telegram session if its session file exists on a server with HTTP auth enabled, reading and sending messages as that account. Upgrade to 0.19.1.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 9.4 | Critical | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0065, the 51st percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:40 UTC First seen by agentprime
- 31 Oct 2026, 14:40 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-rxw2-pc8j-vxwm
- OSV: GHSA-rxw2-pc8j-vxwm
- github.com/leshchenko1979/fast-mcp-telegram/security/advisories/GHSA-rxw2-pc8j-vxwm
- nvd.nist.gov/vuln/detail/CVE-2026-52830
- github.com/alexeyleshchenko/fast-mcp-telegram
- github.com/pypa/advisory-database/tree/main/vulns/fast-mcp-telegram/PYSEC-2026-2473.yaml
- pypi.org/project/fast-mcp-telegram
- web.archive.org/web/20250926152207/https://github.com/leshchenko1979/fast-mcp-telegram