CVE-2026-55096

published 28 Sep 2026 · updated 1 Oct 2026

SSRF via DNS-resolution gap in _validate_url_security (file download by URL)

7.1HighCVSS 7.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

fast-mcp-telegram is a Telegram MCP Server. Prior to version 30.1, the send_message/send_message_to_phone MCP tools accept files as a list of http(s) URLs, which the server downloads and attaches to the outgoing Telegram message. Downloads are guarded by _validate_url_security, an SSRF denylist that checks the URL's literal hostname string but never resolves DNS. The fetch (httpx.AsyncClient.get) does its own resolution at request time. Consequently a hostname that resolves to a loopback / private / link-local address passes the guard and is fetched — even with the secure defaults block_private_ips=True and allow_http_urls=False. Because the fetched body is returned to the attacker as a Telegram file attachment, this is a full-read, exfiltrating SSRF, not blind. This issue has been patched in version 30.1.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
leshchenko1979<30.1

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-55096 severity on Zeptric[![CVE-2026-55096](https://zeptric.io/badge/cve/CVE-2026-55096.svg)](https://zeptric.io/cve/CVE-2026-55096)