CVE-2026-55096CWE-184CWE-918ssrf

CVE-2026-55096

High · published September 28, 2026

CVSS v3.1
7.1
EPSS
0%
Percentile
9.9
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS v3.1
7.1 · HIGH
Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
CVSS v4.0
Not supplied
EPSS
0.00205 · 9.9th percentile
Weaknesses
CWE-184 · Incomplete List of Disallowed Inputs; CWE-918 · Server-Side Request Forgery (SSRF)
Published
2026-09-28T21:17Z
References (4)
EPSS history
Timeline
  • 30 SEP 03:27Z
    EPSS moved — → 0%
    epss
  • 28 SEP 16:38Z
    SSRF via DNS-resolution gap in _validate_url_security (file download by URL)
    cvelistv5