Threat reportVulnerabilityTL-2026-1190
CVE-2026-52830: Path Traversal in fast-mcp-telegram Bearer Token Validation Exposes Telegram Session Files
fast-mcp-telegram, a Python/PyPI Model Context Protocol (MCP) server that bridges Telegram accounts to AI assistants and HTTP clients, fails to sanitize HTTP Bearer tokens before joining them into a session-file path. An unauthenticated remote attacker can supply a traversal-crafted token such as `../fast-mcp-telegram/telegram` to bypass the server's reserved-token blocklist and authenticate as the default legacy Telegram session at `~/.config/fast-mcp-telegram/telegram.session`, gaining full MTProto API access (read/send messages, invoke all account-prefixed MCP tools).
Key facts
| Identifiers | TL-2026-1190, CVE-2026-52830 |
|---|---|
| Also known as | GHSA-rxw2-pc8j-vxwm |
| Severity | CRITICAL |
| CVSS | 9.4 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L) |
| EPSS | CVE-2026-52830: 0.6% (49.5th percentile) |
| Affected products | leshchenko1979 fast-mcp-telegram |
| Weaknesses (CWE) | CWE-22, CWE-287 |
| Tools | MTProto API |
| MITRE ATT&CK techniques | T1005 Data from Local System, T1036 Masquerading, T1059 Command and Scripting Interpreter, T1071 Application Layer Protocol, T1078 Valid Accounts, T1087 Account Discovery, T1098 Account Manipulation, T1102 Web Service, T1133 External Remote Services, T1190 Exploit Public-Facing Application, T1211 Exploitation for Stealth, T1213 Data from Information Repositories and 6 more in the attack flow |
| Motivation | UNKNOWN |
| Target sectors | technology, ai-services |
| Target regions | Global |
| Detection rules | 9 (1 shown free) |
| Sources | 11 cited sources |
Detection coverage
As of 2026-07-10, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-1190 across Splunk SPL, Microsoft KQL and Sigma, covering 16 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: CVE-2026-52830 — Reserved Session Filename Resolved from Non-Literal Bearer Token
Detects successful MCP authentication events where the resolved session-file path matches the reserved default filename (telegram.session) even though the raw supplied Bearer token was not the literal string 'telegram' — the concrete post-exploitation signature of the blocklist bypass granting default-account access.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1528, T1078, T1552
- Data sources: fast-mcp-telegram application auth logs, sysmon file_event, windows_security
- Severity: critical
- Confidence: high
Splunk SPL
index=app sourcetype="fast-mcp-telegram:auth"
| eval token_literal=if(match(bearer_token, "^telegram$"), "literal", "non_literal")
| where resolved_session_path="*telegram.session" AND token_literal="non_literal" AND auth_result="success"
| table _time, src_ip, bearer_token, resolved_session_path, auth_result, account_scope
| sort -_timeMicrosoft KQL
DeviceFileEvents
| where TimeGenerated > ago(24h)
| where FolderPath has "fast-mcp-telegram" and FileName == "telegram.session"
| join kind=inner (
DeviceProcessEvents
| where ProcessCommandLine has "Authorization" and ProcessCommandLine has "Bearer"
| where not(ProcessCommandLine has "Bearer telegram")
) on DeviceName
| project TimeGenerated, DeviceName, FileName, InitiatingProcessAccountName, ProcessCommandLineSigma
title: MCP Server Reserved Session Filename Access via Non-Literal Token
id: 4d7c9a10-6b3e-4f21-9a8e-1c2d3e4f5190
status: experimental
description: Detects file access to a reserved default session filename (e.g. telegram.session) resolved from a non-literal/traversal-containing bearer token, indicating a reserved-token-blocklist bypass.
references:
- https://github.com/advisories/GHSA-rxw2-pc8j-vxwm
author: Threadlinqs Team
date: 2026-07-10
tags:
- attack.credential-access
- attack.t1528
- attack.t1078
- attack.tool.fast_mcp_telegram
- cve.2026.52830
logsource:
category: file_event
product: linux
detection:
selection:
TargetFilename|endswith: 'telegram.session'
Image|contains: 'python'
filter_literal:
CommandLine|contains: 'token=telegram'
condition: selection and not filter_literal
falsepositives:
- Legitimate default-account owner authenticating with the literal 'telegram' token from an approved host
level: mediumKnown false positives:
- Legitimate operator re-authenticating the default session with an unusual but non-malicious token format
Tuning notes: Enrich with the raw bearer_token field to confirm the resolved-vs-literal mismatch rather than relying on filename alone; baseline the known set of authorized session-owner source IPs/hosts to suppress expected traffic.
- MCP Endpoint Reconnaissance Preceding Bearer Token Traversal Exploit · unlock with TL Creds
- Bearer Token Alphabet Violation Reaching Authentication Success · unlock with TL Creds
- Default-Account Session Discovery via Account-Prefix Bypass · unlock with TL Creds
- Sigma — Traversal-Crafted Bearer Token in Reverse Proxy Access Log · unlock with TL Creds
- Sigma — Reserved Session File Access via Non-Literal Bearer Token (Valid Accounts / Steal Access Token) · unlock with TL Creds
- Sigma — MTProto C2/Exfiltration Burst on Default Account After Bypass Auth · unlock with TL Creds
- CVE-2026-52830 — Path Traversal Sequence in MCP Bearer Authorization Header · unlock with TL Creds
- CVE-2026-52830 — Anomalous MTProto Tool Invocation Following Traversal Bypass Auth · unlock with TL Creds
Indicators of compromise
As of 2026-07-10, Threadlinqs Intelligence tracks 16 indicators of compromise for TL-2026-1190.
Technical analysis
All versions up to 0.19.0 are affected; fixed in 0.19.1.
fast-mcp-telegram exposes an HTTP-accessible MCP (Model Context Protocol) server that lets AI assistants and HTTP clients drive a Telegram account through MTProto. To support multiple concurrent Telegram sessions over HTTP, the server authenticates each request with a Bearer token and resolves that token to a session file on disk via `SessionFileTokenVerifier.verify_token()`, which constructs the path as `session_dir / f"{token}.session"`.
To stop HTTP clients from silently reusing the operator's own default account, the verifier explicitly denies tokens whose lowercase value matches a small reserved-name list, including the literal string `telegram` (the default session's base filename). However, the verifier never normalizes the token or rejects path separators, `..` segments, or absolute paths before performing this check and before joining the token into the filesystem path. Because the blocklist compares only the raw token string, an attacker can trivially route around it: a token such as `../fast-mcp-telegram/telegram` does not equal the literal string `telegram`, so the blocklist check passes, yet when joined and resolved on disk it points at the exact same file, `~/.config/fast-mcp-telegram/telegram.session` (the config/session directory is itself named `fast-mcp-telegram`, so a single `../` traversal segment plus the real filename recreates the original path).
Once the traversal-crafted Bearer token resolves to an existing session file, the verifier treats the request as successfully authenticated as that session's owner, entirely without any prior authentication, valid credential, or user interaction (CVSS 3.1 AV:N/AC:L/PR:N/UI:N). The attacker is now driving the default (typically privileged, first-configured) Telegram account through every MCP tool exposed by the server: reading and sending messages and attachments, enumerating chats/contacts, and issuing arbitrary MTProto API calls available to that session. This holds even in deployments that intentionally enable per-user, account-prefixed MCP tools specifically to prevent HTTP multi-tenant clients from ever touching the default account — the path-traversal bypass defeats that isolation control entirely, collapsing the server's authentication model down to unauthenticated full-account access. Confidentiality and integrity impact are both High; availability impact is Low (the flaw does not directly enable session/file destruction), yielding the published CVSS 3.1 base score of 9.4 (Critical), vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L.
The flaw is dual-classified CWE-22 (Improper Limitation of a Pathname to a Restricted Directory / Path Traversal) and CWE-287 (Improper Authentication), reflecting that the root defect is a path-normalization failure but the security consequence is a full authentication bypass. It was reported by researcher DavidCarliez, assigned GHSA-rxw2-pc8j-vxwm by the GitHub Advisory Database and CVE-2026-52830, and published July 2, 2026 (NVD last modified July 6, 2026), with broad security-press coverage (Cyber Security News, GBHackers, TheHackerWire, Cryptika, Rankiteo) starting July 7, 2026. It was fixed in fast-mcp-telegram 0.19.1 by enforcing a safe token alphabet, rejecting traversal/absolute-path characters, and verifying the resolved path stays within the configured session directory.
The vulnerability sits within a broader 2026 pattern of MCP ecosystem insecurity: independent research (VIPER-MCP scanning ~39,884 public MCP repositories; Censys internet scanning) found 106 zero-day-class MCP vulnerabilities, roughly 12,520 publicly exposed MCP services (~40% with no authentication at all), 43% of servers carrying command-injection-class flaws, and 79% handling credentials in plaintext, with over 30 CVEs filed against MCP servers between January and February 2026 alone. This CVE maps directly to two OWASP MCP Top 10 categories: MCP07 (Insufficient Authentication and Authorization) and, via its file-path handling root cause, the path-traversal-heavy execution-layer risks OWASP groups under MCP05 (Command Injection and Execution), where surveyed MCP servers showed an 82% path-traversal exposure rate.
No in-the-wild exploitation or attacker-controlled IOCs (C2 domains/IPs, malware) had been reported at time of writing; a proof-of-concept demonstrating the traversal bypass was confirmed by security researchers but not published with operational indicators.
MITRE ATT&CK techniques by tactic:
Collection
T1005 Data from Local System; T1213 Data from Information Repositories
Defense Evasion
T1036 Masquerading; T1211 Exploitation for Stealth
Execution
T1059 Command and Scripting Interpreter
Command and Control
T1071 Application Layer Protocol; T1102 Web Service
Initial Access
T1078 Valid Accounts; T1133 External Remote Services; T1190 Exploit Public-Facing Application
Persistence
T1078 Valid Accounts; T1098 Account Manipulation
Discovery
T1087 Account Discovery; T1518 Software Discovery
Credential Access
T1528 Steal Application Access Token; T1552 Unsecured Credentials
Exfiltration
T1567 Exfiltration Over Web Service
Reconnaissance
T1595 Active Scanning; T1596 Search Open Technical Databases
Remediation
Patches
- fast-mcp-telegram 0.19.1 — normalizes and validates Bearer tokens, rejects path traversal sequences, verifies resolved session path remains inside the session directory
Immediate actions
- Upgrade fast-mcp-telegram to version 0.19.1 or later immediately
- Rotate/regenerate the default Telegram session file and any Bearer tokens issued before the upgrade
- Restrict network exposure of the fast-mcp-telegram HTTP endpoint to trusted networks (VPN/allowlist) until patched
- Audit HTTP access logs for Authorization/Bearer header values containing '..', '/', '\\', or matching known bypass patterns like '../fast-mcp-telegram/telegram'
Workarounds
- Disable HTTP Bearer-token multi-session access and restrict the server to trusted local/stdio MCP transport only until upgraded
- Front the HTTP endpoint with a reverse proxy that strips/rejects Authorization headers containing '/', '\\', or '..' sequences
Longer-term hardening
- Enforce a strict, allow-listed token alphabet (e.g. URL-safe base64, 32-128 chars) for all bearer-token-to-filesystem-path mappings
- Reject any token containing path separators, '..', or resolving outside the configured session directory before any filesystem access
- Verify the fully resolved (canonicalized) session path is a strict child of the intended session directory (realpath/containment check) rather than relying on string blocklists
- Apply the same path-containment validation consistently across every authentication and token-handling code path in the server
- Add MCP-specific security review to the SDLC: reference OWASP MCP Top 10 (MCP07 Insufficient Authentication and Authorization; MCP05 Command Injection and Execution) during design and code review
- Add regression tests specifically covering traversal-sequence and reserved-name-bypass bearer tokens
Affected and fixed versions
- leshchenko1979 — fast-mcp-telegram
Vulnerable versions: <=0.19.0
Fixed in: 0.19.1
Timeline
- Maintainer leshchenko1979 initially publishes the security advisory for the fast-mcp-telegram repository, identifying the flaw in current `master` commit 167ab705f1cd09b21e85c370570471fe75a4f8c9 and release tag 0.19.0, ahead of the formal CVE Advisory Database listing.
- GitLab Advisory Database and GitHub Advisory Database (GHSA-rxw2-pc8j-vxwm) publish and mark 'Reviewed' detailed advisories describing the Bearer-token path-traversal bypass in fast-mcp-telegram's SessionFileTokenVerifier.
- CVE-2026-52830 assigned and published (source: GitHub, Inc.) with CVSS 3.1 base score 9.4 (Critical), vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L; new CVE record received by NVD from GitHub, Inc. at 17:16:56 UTC.
- NVD record for CVE-2026-52830 last-modified timestamp updates to syndicate the GitHub-sourced CVSS assessment; NVD explicitly flags the record as 'not being prioritized for NVD enrichment efforts due to resource or other concerns,' leaving GitHub's CVSS scoring as authoritative.
- CISA-ADP (Authorized Data Publisher) submits a modification to the CVE-2026-52830 record at 12:16:34 UTC, the second change record logged against the CVE.
- Security researchers confirm a controlled proof-of-concept exploiting the traversal bypass; no in-the-wild exploitation or attacker-controlled indicators reported as of this date.
- fast-mcp-telegram version 0.19.1, which enforces strict token-alphabet validation and session-path containment checks, confirmed available on PyPI as the remediation for all versions <=0.19.0.
- Broad security-press coverage begins (Cyber Security News, GBHackers, TheHackerWire, Cryptika, Rankiteo), publicizing the vulnerability, exploit mechanics, and researcher attribution to DavidCarliez.
Sources cited
- CVE-2026-52830 Detail - NVD NVD (NIST) · Advisory · 2026-07-02
- CVE-2026-52830: fast-mcp-telegram: Bearer token path traversal bypasses reserved Telegram session protection GitLab · Advisory · 2026-07-02
- fast-mcp-telegram vulnerabilities kodemsecurity.com · Vendor report · 2026-07-07
- OWASP MCP Top 10: A Guide to Securing Model Context Protocol in 2026 cycode.com · Research · 2026-01-01
- GHSA-rxw2-pc8j-vxwm — fast-mcp-telegram GitHub Security Advisory GitHub · Code repository · 2026-07-02
- Archived fast-mcp-telegram GitHub repository web.archive.org · Code repository · 2025-09-26
- Critical fast-mcp-telegram Vulnerability Lets Attackers Access Telegram Session Without Token blog.rankiteo.com · Blog · 2026-07-07
- Critical fast-mcp-telegram Vulnerability Lets Attackers Access Telegram Session Without Token cybersecuritynews.com · News · 2026-07-07
- Critical fast-mcp-telegram Vulnerability Lets Attackers Access Telegram Session Without Token gbhackers.com · News · 2026-07-07
- fast-mcp-telegram Critical Path Traversal Session Bypass (CVE-2026-52830) thehackerwire.com · News · 2026-07-07
- Fast-mcp-telegram Vulnerability Allow Attackers to Access Sensitive Files cryptika.com · News · 2026-07-07
Previous and next in vulnerability
Drafted by the Threadlinqs research pipeline from 11 sources; published ; last updated —.