UTC
Critical

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

CVE-2026-52830 · GHSA-rxw2-pc8j-vxwm · published 2026-07-02 · updated 2026-08-13

Severity
Critical
CVSS score
9.4
Chance of exploitation (EPSS)
0.65%
Fixed in
0.19.1
  • Exploitation Public proof of concept
  • Automatable Yes
  • Technical impact Partial
  • CISA SSVC
What it is

An unauthenticated network client can access the Telegram account represented by the default telegram.session file without knowing a generated bearer token, if that legacy or default session file is present on a server running HTTP auth. The attacker can then call Telegram MCP tools as that account, including message reading, message sending, MTProto API calls, and attachment-producing tool surfaces available to the session.

What to do

Upgrade fast-mcp-telegram to 0.19.1 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

Reject bearer tokens that are not strict opaque token identifiers before using them in file paths. Recommended checks: 1. Accept only a safe token alphabet, for example ^[A-Za-z0-9_-]{32,128}$, matching generated URL-safe base64 tokens. 2. Reject /, \\, ., .., empty segments, and absolute paths for both header auth and URL auth. 3. Resolve the final session path and require it to remain directly under the configured session directory: 4. Apply the same validation in SessionFileTokenVerifier, URL auth middleware, setup flows, cleanup code, and any code that opens session files by token. 5.

Affected
PackageRegistryAffectedFixed in
fast-mcp-telegramPyPI<= 0.19.00.19.1

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].