Vulnerability record

CVE-2026-52830

A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.

Full record read. Reported values and explicit gaps below come from the tracked record. Tracker snapshot: Aug 8, 2026.

What it is

Reported

fast-mcp-telegram is a Telegram MCP Server. Prior to 0.19.1, fast-mcp-telegram validates HTTP Bearer tokens by joining the raw token string into a session-file path. The verifier rejects the exact reserved token telegram, but it does not reject path separators or normalize the path before checking whether the session file exists. A remote HTTP client can therefore authenticate as the default legacy session with a token such as ../fast-mcp-telegram/telegram when the documented default session file ~/.config/fast-mcp-telegram/telegram.session exists.… Source description excerpt; complete tracked detail loads below.

NVD published: Jul 3, 2026 · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

What is affected

Reported

fast-mcp-telegram — fast-mcp-telegram. Product-level identification only; no affected-version conclusion is available from this field.

NVD published: Jul 3, 2026 · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

Urgency and basis

Reported

Track* · 230.7

Tracker decision tier from the evidence detailed below · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

Exploitation evidence

Not reported

Not reported by tracked sources.

What to do

Reported

A source remediation link is available. Validate that guidance against the affected product and your environment.

Source remediation ↗

Tracked source remediation field · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

Evidence detail

Loading the full tracker evidence record…