CVE-2026-55096

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

State
Published
Severity
7.1 High
Published
Sep 28, 2026
Updated
Oct 1, 2026
Reserved
Jun 16, 2026

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
3.17.1 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:NGitHub_M

Weaknesses

  • CWE-184 Incomplete List of Disallowed Inputs
  • CWE-918 Server-Side Request Forgery (SSRF)

Affected Products

ProductVersions
fast-mcp-telegramleshchenko1979
  • < 30.1Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.