Skip to content

AAK-MCP-FASTMCPTELEGRAM-CVE-2026-55096-001: fast-mcp-telegram below 0.30.1 fetches attachment URLs its SSRF guard never resolved

Severity
HIGH
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py
Auto-fixable
No.
SARIF name
FastMcpTelegramAttachmentSsrf

What it detects

fast-mcp-telegram, a Telegram MCP server, downloads the http(s) URLs given to its send_message and send_message_to_phone MCP tools and attaches them to the outgoing message. Before 0.30.1 the guard, _validate_url_security, compares the URL's literal hostname with a denylist and never resolves it, while the fetch (httpx.AsyncClient.get) resolves the name itself. A hostname that resolves to a loopback, private or link-local address therefore passes the guard and is fetched, even with block_private_ips=True and allow_http_urls=False, and the body comes back to the caller as a Telegram attachment, so the read is not blind (CVE-2026-55096, CVSS 3.1 7.1, CWE-918/CWE-184). 0.30.1 resolves the name with socket.getaddrinfo and blocks loopback, private and link-local results (fix commit e6b3032c). NVD and the advisory print the fixed version as "30.1"; the release on PyPI and the GitHub tag are 0.30.1.

How to fix

Upgrade fast-mcp-telegram to >= 0.30.1 and pin it. Until then, do not let an untrusted caller choose the attachment URLs send_message downloads, or run the server where loopback, private and cloud-metadata addresses are unreachable.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-FASTMCPTELEGRAM-CVE-2026-55096-001

Limitations

Reports a reference that names the package: a requirements, pyproject or lockfile entry, or fast-mcp-telegram in an MCP config, where an unpinned uvx fast-mcp-telegram is reported as unpinned, as for the other PyPI pins. It reads versions, not code: the defect's shape, a hostname-only guard before a fetch that resolves again, is the class AAK-SSRF-TOCTOU-001 names, which recognises this guard in code since #855 and keeps firing on 0.30.1's source, whose fetch still resolves the name a second time. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-FASTMCPTELEGRAM-CVE-2026-55096-001.md: the page then shows that text, with the registry reference appended under it.