Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-52830Published 2026-07-02

CVE-2026-52830 — leshchenko1979 fast-mcp-telegram

critical

As of 2026-07-10, CVE-2026-52830 is a CRITICAL-severity vulnerability in leshchenko1979 fast-mcp-telegram, CVSS v3.1 9.4, EPSS 0.6% (49.5th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-52830, most recently “CVE-2026-52830: Path Traversal in fast-mcp-telegram Bearer Token Validation Exposes Telegram Session Files”.

CVSS v3.1
9.4/10Critical
EPSS
0.6%Higher than 49.5% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
1Campaigns referencing it
Priority
6.7/10Threadlinqs triage score
Published
Updated 2026-07-10
CVSS v3.1 9.4 (CRITICAL) · EPSS 0.6% (higher than 49.5% of all scored CVEs) · Priority 6.7/10 · Published 2026-07-02

Last updated:

What is CVE-2026-52830?

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. This bypasses the reserved session name control that is intended to prevent HTTP multi-user sessions from colliding with the default stdio or legacy account. With account-prefixed MCP tools enabled, the attacker still sees and calls the prefixed tools for the default account, so the prefix middleware does not stop the session selection bypass. This vulnerability is fixed in 0.19.1.

The record classifies CVE-2026-52830 under weakness classes CWE-22, CWE-287. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 140 days ago.

Severity and exploitation probability

CVSS v3.1 base score
9.4 — CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
EPSS (FIRST)
0.6% probability of exploitation in the next 30 days, higher than 49.5% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
6.7/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-07-02

Is CVE-2026-52830 being exploited?

It currently carries a trending score of 22 in the Threadlinqs vulnerability feed.

Affected products and versions

  • leshchenko1979: fast-mcp-telegram

How to fix CVE-2026-52830

No vendor patch reference has been recorded for CVE-2026-52830 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-52830

1 tracked threat in the Threadlinqs corpus references CVE-2026-52830, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, FIRST EPSS.

Vendor advisory and patch

Other references