# fast-mcp-telegram: Bearer token path traversal bypasses reserved Telegram session protection

Advisory record · `GHSA-rxw2-pc8j-vxwm`

- **Identifiers:** `GHSA-rxw2-pc8j-vxwm` · `CVE-2026-52830` · `PYSEC-2026-2473`
- **State:** Confirmed
- **Severity:** CVSS 9.4 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html) · [CWE-287](https://cwe.mitre.org/data/definitions/287.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md) · [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 2 Jul 2026
- **Updated:** 13 Aug 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 2 Jul 2026, 20:38 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.4: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `fast-mcp-telegram` (PyPI): affected `<0.19.1`; fixed in `0.19.1`

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

Written 5 Nov 2026.

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

- 9.4 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L`, from 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](https://osv.dev/vulnerability/GHSA-rxw2-pc8j-vxwm)

## Sources

- [GitHub Advisory Database: GHSA-rxw2-pc8j-vxwm](https://github.com/advisories/GHSA-rxw2-pc8j-vxwm)
- [OSV: GHSA-rxw2-pc8j-vxwm](https://osv.dev/vulnerability/GHSA-rxw2-pc8j-vxwm)
- <https://github.com/leshchenko1979/fast-mcp-telegram/security/advisories/GHSA-rxw2-pc8j-vxwm>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-52830>
- <https://github.com/alexeyleshchenko/fast-mcp-telegram>
- <https://github.com/pypa/advisory-database/tree/main/vulns/fast-mcp-telegram/PYSEC-2026-2473.yaml>
- <https://pypi.org/project/fast-mcp-telegram>
- <https://web.archive.org/web/20250926152207/https://github.com/leshchenko1979/fast-mcp-telegram>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-rxw2-pc8j-vxwm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-rxw2-pc8j-vxwm/>. Everything for agents: <https://agentprime.io/llms.txt>.
