Home › Guides › MCP Servers and SSRF
✓ checked 17 October 2026 · sources: GitHub Advisory Database, NVD, PyPI, pypistats.org, Docker Hub, the official MCP Registry · method · caveats · download the data
GitHub’s reviewed advisory database has published 642 server-side request forgery (SSRF) advisories so far in 2026, against 96 in all of 2025. SSRF is the bug where a server can be told to fetch an address it shouldn’t, such as an internal network or a cloud metadata service, so the server acts as an unintended proxy. 54 of these advisories concern Model Context Protocol (MCP) servers and tools, the plug-ins AI assistants use to reach the web and other systems.
SSRF advisories, 2026 so far 642involving MCP 54mcp-server-fetch downloads, last month 506,506
Headline findings
- SSRF has more than doubled as a share of advisories. SSRF advisories were 2.7% of the 3,569 reviewed advisories published in 2025 and 5.8% of the 11,037 published in 2026 to date; by count, 2026 already has 6.7 times 2025’s total. April was the busiest month, with 101.
- MCP advisories cluster around repeat fixes. 51 of the 54 MCP-related SSRF advisories were published in 2026, 10 of them in September. 7 are for mcp-atlassian, 5 of them published on 22 September, and 17 of the 54 have “bypass” or “incomplete” in their summary, meaning an existing SSRF protection or an earlier fix did not hold.
- The reference fetch server now blocks internal addresses by default. CVE-2026-104120, published by NVD on 2 October with VulDB as the numbering authority, says manipulating the URL in mcp-server-fetch’s fetch tool “leads to server-side request forgery” in versions “up to 2026.6.4”, and that “The pull request to fix this issue awaits acceptance”. That pull request was closed without merging on 5 October. Instead, version 2026.10.10, uploaded to PyPI on 11 October, includes a change that refuses private, loopback and metadata addresses; its documentation says that by default the server “refuses to fetch private, loopback, link-local and other non-public addresses, including cloud metadata endpoints”, but that the check “does not protect against DNS rebinding between that check and the connection”. The previous release, 2026.8.18, has no such check. As of 17 October, neither NVD’s record (scored 5.5 under CVSS 4.0 by VulDB) nor GitHub’s unreviewed copy names a fixed version. mcp-server-fetch had 506,506 PyPI downloads in the past month, according to pypistats.org.
- The Docker image predates the change. Docker Hub’s mcp/fetch image has 1,921,500 pulls, and its only tag, latest, was last pushed on 7 July 2026, before 2026.10.10 was released. We did not inspect the image, so we can’t say which version of the server it contains or whether it is affected. For comparison, mcp/playwright has 2,487,953 pulls.
- Few registry servers are about proxies; more fetch the web. Of 44,716 active servers in the official MCP Registry, 1,153 match keywords for scraping, crawling, browser automation or fetching web pages. In a random sample of 60 of those we checked by hand, 39 let an agent fetch, scrape or browse arbitrary pages; the rest used the words for narrower tools such as site audits. Of 208 servers mentioning proxies, we judged 44 to sell, manage or route requests through web proxies and 5 to detect them; most of the others are gateways that sit between AI clients and other MCP servers.
SSRF advisories per month
Every MCP-related SSRF advisory
| Published | Package | ID | Summary | GitHub severity |
|---|---|---|---|---|
| 2 Oct 2026 | github.com/siyuan-note/siyuan/kernel | GHSA-x8gv-g2g3-65fj | SiYuan Agent Tools SSRF via DNS-Rebinding TOCTOU (Bypass of CheckHostSSRF) | high |
| 2 Oct 2026 | rmcp | GHSA-c9xm-49cp-xcr9 | rmcp OAuth client fetches server-controlled resource_metadata URLs | medium |
| 22 Sep 2026 | mcp-atlassian | CVE-2026-77249 | MCP Atlassian: Incomplete fix for GHSA-7r34-79r5-rcc9: redirect-based SSRF via unhooked requests session in Jira user-permission lookup | medium |
| 22 Sep 2026 | mcp-atlassian | CVE-2026-77274 | MCP Atlassian: SSRF Protection Bypass | high |
| 22 Sep 2026 | mcp-atlassian | CVE-2026-77267 | mcp-atlassian has an incomplete SSRF remediation | high |
| 22 Sep 2026 | mcp-atlassian | CVE-2026-77261 | MCP Atlassian: SSRF redirect protection missing for basic-auth and OAuth authentication branches | high |
| 22 Sep 2026 | mcp-atlassian | CVE-2026-77265 | MCP Atlassian: SSRF via DNS Rebinding in Header-Based Authentication Flow | medium |
| 22 Sep 2026 | @aborruso/ckan-mcp-server | CVE-2026-61612 | @aborruso/ckan-mcp-server has SSRF via DNS-name → internal IP — incomplete fix of CVE-2026-53509 | medium |
| 18 Sep 2026 | github.com/obot-platform/obot | GHSA-jgh3-fggc-mcpm | Obot: Server-Side Request Forgery via remote MCP server URL | high |
| 15 Sep 2026 | @zereight/mcp-gitlab | CVE-2026-61559 | @zereight/mcp-gitlab Vulnerable to Server-Side Request Forgery | critical |
| 11 Sep 2026 | mcp-from-openapi @frontmcp/adapters frontmcp | CVE-2026-59973 | FrontMCP and mcp-from-openapi have bypass of OpenAPI external $ref SSRF fix | high |
| 2 Sep 2026 | @aborruso/ckan-mcp-server | CVE-2026-73845 | CKAN MCP Server: MQA server allowlist bypass via unanchored regex (`isValidMqaServer`) | medium |
| 25 Aug 2026 | chainlit | CVE-2026-45019 | Chainlist has SSRF via MCP SSE and streamable-http transports that allows unauthenticated internal network access | high |
| 19 Aug 2026 | mcp-searxng | CVE-2026-54689 | SearXNG MCP Server: Additional hardened-mode SSRF bypasses | medium |
| 19 Aug 2026 | mcp-searxng | CVE-2026-54688 | SearXNG MCP Server is Vulnerable to SSRF in web_url_read: the internal-address guard is disabled by default (MCP_HTTP_HARDEN off) | medium |
| 19 Aug 2026 | @contentful/mcp-server @contentful/mcp-tools | CVE-2026-53957 | Contentful MCP Server: export_space/import_space tools pass LLM-controlled `host`/`proxy` args to CMA client, redirecting server PAT to attacker-controlled endpoint | high |
| 14 Aug 2026 | mcp-contextforge-gateway | CVE-2026-53708 | ContextForge: DNS TOCTOU race condition causes SSRF protection bypass (`/admin/gateways/test`) | medium |
| 30 Jul 2026 | flyto-core | CVE-2026-67428 | Flyto2 Core: Multiple HTTP-family modules fetch client-controlled URLs without the SSRF guard their siblings apply (SSRF to internal/metadata) | high |
| 24 Jul 2026 | @frontmcp/adapters | GHSA-8q49-2h5h-434x | FrontMCP: Server-Side Request Forgery (SSRF) in the OpenAPI adapter spec-change poller | medium |
| 22 Jul 2026 | n8n n8n | GHSA-vhf8-cg2h-cg3p | n8n: SSRF Protection Bypass via MCP Client Node | medium |
| 17 Jul 2026 | meta-ads-mcp | CVE-2026-54549 | meta-ads-mcp: Server-Side Request Forgery (SSRF) in `upload_ad_image` via Unrestricted `image_url` Fetch | high |
| 15 Jul 2026 | github.com/stacklok/toolhive | CVE-2026-58196 | ToolHive: SSRF in remote MCP server authentication discovery (host-side, bypasses container isolation) | low |
| 10 Jul 2026 | mcp-atlassian | GHSA-489g-7rxv-6c8q | MCP Atlassian: DNS-rebinding TOCTOU bypass of the SSRF fix (CVE-2026-27826) | medium |
| 7 Jul 2026 | @aborruso/ckan-mcp-server | CVE-2026-53509 | @aborruso/ckan-mcp-server: SSRF via base_url allows access to internal networks (Potential fix bypass of CVE-2026-33060) | medium |
| 1 Jul 2026 | @apify/actors-mcp-server | CVE-2026-50143 | Apify Model Context Protocol (MCP) server: Actor MCP path authority injection leaks Apify token | high |
| 1 Jul 2026 | auth-fetch-mcp | CVE-2026-49857 | auth-fetch-mcp has SSRF Protection Bypass via IPv4-mapped IPv6 Loopback | high |
| 1 Jul 2026 | @jshookmcp/jshook | CVE-2026-49856 | @jshookmcp/jshook: ICMP probe and traceroute skip local-network SSRF authorization | medium |
| 26 Jun 2026 | @cardano402/mcp-server | GHSA-rp72-5v5q-2446 | @cardano402/mcp-server missing spending limits, LAN-exposed HTTP transport, and SSRF via catalog.server.url | low |
| 21 Jun 2026 | litellm | CVE-2026-12798 | BerriAI litellm has SSRF via Unvalidated spec_path URL in MCP OpenAPI Spec Loader | low |
| 19 Jun 2026 | mcp-searxng | GHSA-mrvx-jmjw-vggc | SearXNG MCP Server: DNS-resolved Private Hostname SSRF in `web_url_read` | high |
| 19 May 2026 | auth-fetch-mcp | GHSA-hv85-774v-26fg | auth-fetch-mcp: SSRF and disk exfiltration via unvalidated auth_fetch and download_media URLs | high |
| 18 May 2026 | org.springaicommunity:mcp-client-security | CVE-2026-45609 | Spring AI MCP Security: Unvalidated URL Fetching (SSRF) | high |
| 8 May 2026 | github.com/modelcontextprotocol/registry | CVE-2026-44430 | MCP Registry has an unauthenticated SSRF: HTTP namespace verification dials 6to4 / NAT64 / site-local IPv6 addresses, bypassing private-address allowlist | medium |
| 8 May 2026 | github.com/modelcontextprotocol/registry | CVE-2026-44428 | MCP Registry’s GitHub OIDC tokens are replayable across registry deployments due to shared audience | low |
| 8 May 2026 | n8n-mcp | GHSA-8g7g-hmwm-6rv2 | n8n-mcp affected by path traversal, redirect-following SSRF, and telemetry payload exposure | high |
| 8 May 2026 | n8n-mcp | CVE-2026-44694 | n8n-mcp webhook and API client paths has an authenticated SSRF | high |
| 5 May 2026 | open-websearch | CVE-2026-42260 | open-websearch has SSRF in `fetchWebContent` MCP tool: bracketed IPv6 literals and non-resolving hostname check bypass `isPrivateOrLocalHostname` | high |
| 30 Apr 2026 | n8n-mcp | CVE-2026-42449 | n8n-mcp’s IPv4-mapped IPv6 addresses bypass SSRF protection in validateUrlSync(), enabling full SSRF for SDK embedders | high |
| 27 Apr 2026 | mcp-url-downloader | CVE-2026-7158 | mcp-url-downloader has a Server-Side Request Forgery issue | medium |
| 27 Apr 2026 | auto-favicon | CVE-2026-7150 | auto-favicon has a Server-Side Request Forgery issue | low |
| 13 Apr 2026 | github.com/apache/skywalking-mcp | CVE-2026-34476 | Apache SkyWalking MCP: Server-Side Request Forgery via SW-URL Header in MCP Server | high |
| 9 Apr 2026 | api-lab-mcp | CVE-2026-5832 | api-lab-mcp vulnerable to SSRF | medium |
| 8 Apr 2026 | n8n-mcp | CVE-2026-39974 | n8n-mcp has authenticated SSRF via instance-URL header in multi-tenant HTTP mode | high |
| 8 Apr 2026 | mcp-from-openapi @frontmcp/sdk @frontmcp/adapters | CVE-2026-39885 | mcp-from-openapi is Vulnerable to SSRF via $ref Dereferencing in Untrusted OpenAPI Specifications | high |
| 2 Apr 2026 | a11y-mcp | CVE-2026-5323 | a11y-mcp: Server-Side Request Forgery (SSRF) vulnerability in A11yServer function | low |
| 31 Mar 2026 | fastmcp | CVE-2026-32871 | FastMCP OpenAPI Provider has an SSRF & Path Traversal Vulnerability | critical |
| 18 Mar 2026 | @aborruso/ckan-mcp-server | CVE-2026-33060 | SSRF in @aborruso/ckan-mcp-server via base_url allows access to internal networks | medium |
| 12 Mar 2026 | ha-mcp | CVE-2026-32111 | ha-mcp OAuth 2.1 DCR mode enables network reconnaissance via an error oracle | medium |
| 10 Mar 2026 | mcp-atlassian | CVE-2026-27826 | MCP Atlassian has SSRF via unvalidated X-Atlassian-Jira-Url / X-Atlassian-Confluence-Url headers | high |
| 10 Mar 2026 | Azure.Mcp Azure.Mcp @azure/mcp msmcp-azure @azure/mcp | CVE-2026-26118 | Azure MCP Server has Server-Side Request Forgery issue that allows authorized attacker to elevate privileges over a network | high |
| 9 Feb 2026 | mcp-run-python | CVE-2026-25904 | MCP Run Python Deno Sandbox Misconfiguration Allows SSRF Attacks via Localhost Access | medium |
| 10 Dec 2025 | mcp-fetch-server | CVE-2025-65513 | Fetch MCP Server has a Server-Side Request Forgery (SSRF) vulnerability | medium |
| 15 Sep 2025 | hackmd-mcp | CVE-2025-59155 | HackMD MCP Server has Server-Side Request Forgery (SSRF) vulnerability | medium |
| 29 May 2025 | mcp-markdownify-server | CVE-2025-5276 | Markdownify MCP Server allows Server-Side Request Forgery (SSRF) via the Markdownify.get() function | medium |
For proxy-handling bugs in HTTP client libraries such as urllib3 and axios, which many MCP servers use to make their requests, see Proxy Bugs in HTTP Libraries. CVEs in proxy servers and gateways are in the Proxy & AI Gateway CVE Ledger, and the IP ranges AI fetchers use are in AI Fetcher IP Ranges.
SSRF flaws attackers are using: CISA’s list
Added 21 October 2026. The advisories above are reported flaws. A smaller set is known to be used in real attacks. The US Cybersecurity and Infrastructure Security Agency (CISA) keeps a Known Exploited Vulnerabilities (KEV) catalog of flaws it has evidence attackers are using; US federal agencies must fix them by a deadline. Of the catalog’s 1,754 entries on 21 October 2026, 26 are SSRF flaws: named as server-side request forgery or tagged with CWE-918, the weakness category for SSRF.
CISA has added 11 SSRF flaws so far in 2026, more than in 2022, 2023, 2024 and 2025 combined (8). The other 7 were added in 2021, when the catalog launched with many older flaws. Not every 2026 addition is new: 4 of the 11 are CVEs first published in 2020 or 2021 that CISA has only now confirmed are being exploited, and 7 are from 2026.
| Added | CVE | Product | Known ransomware use |
|---|---|---|---|
| 3 Feb 2026 | CVE-2021-39935 | GitLab Community and Enterprise Editions | Not known |
| 17 Feb 2026 | CVE-2020-7796 | Synacor Zimbra Collaboration Suite | Not known |
| 18 Feb 2026 | CVE-2021-22175 | GitLab | Not known |
| 9 Mar 2026 | CVE-2021-22054 | Omnissa Workspace One UEM | Not known |
| 25 Jun 2026 | CVE-2026-20230 | Cisco Unified Communications Manager | Not known |
| 14 Jul 2026 | CVE-2026-15409 | SonicWall SMA1000 Appliances | Yes |
| 19 Aug 2026 | CVE-2026-64849 | MLflow | Not known |
| 2 Sep 2026 | CVE-2026-49869 | Kestra OSS (command injection; also tagged SSRF) | Not known |
| 2 Sep 2026 | CVE-2026-83548 | SonicWall SMA1000 Appliances | Not known |
| 20 Oct 2026 | CVE-2026-96652 | Plex Media Server | Not known |
| 20 Oct 2026 | CVE-2026-96655 | Plex Media Server | Not known |
All SSRF entries added to the KEV catalog in 2026. Ransomware use is CISA’s field. Not known means CISA has not recorded any, not that none has happened. All 26 SSRF entries since 2021 are in the CSV below.
The newest are two flaws in Plex Media Server, the home media-streaming software, added on 20 October 2026 with a deadline of 3 November. CISA added 4 Plex flaws that day and notes that they can be chained together. According to CISA’s descriptions, one lets an attacker with any Plex token make the server send requests to a destination of the attacker’s choice; the other lets an authenticated user make it request arbitrary internal or external addresses. That is the core risk of SSRF covered on this page: a server that can be tricked into fetching on an attacker’s behalf becomes a proxy into networks the attacker can’t reach directly. Plex is often installed on home computers and network storage devices, so a vulnerable server may sit inside a home network. The Plex security notice CISA links to covers Plex Media Server 1.43.2 and earlier.
The 2026 list is otherwise dominated by servers businesses run at the edge of their networks: remote-access appliances from SonicWall, Cisco’s call manager, GitLab, Zimbra email and Omnissa’s device management, plus two AI and automation tools, MLflow and Kestra. For more on flaws in edge devices, see KEV and edge devices; for SSRF and proxy bugs in the HTTP libraries these products use, see Proxy Bugs in HTTP Libraries.
How we checked. We downloaded CISA’s KEV catalog (version 2026.10.21, 1,754 entries) on 21 October 2026 and kept entries whose name or description mentions server-side request forgery or SSRF, or whose weakness list includes CWE-918. The catalog is in the public domain as a work of the US government.
Method
On 17 October 2026 we pulled every GitHub-reviewed advisory tagged CWE-918 from GitHub’s REST API and cross-checked the counts against a copy of GitHub’s advisory-database repository taken the same day; the two matched once 24 withdrawn advisories were removed. Totals of all reviewed advisories come from the repository copy. We counted an advisory as MCP-related if its summary, package names or description mention MCP, then read each match and dropped seven that mention MCP only in passing. CVE details are from the NVD API and GitHub; release details from PyPI, the project’s release notes and the published package files; pulls from Docker Hub’s API. Registry figures are from a full pull of the official MCP Registry’s latest server versions, counting active entries. A separate script recomputes every number from the saved responses.
Caveats
- Advisory counts reflect reporting as well as bugs. GitHub reviewed far more advisories of all kinds in 2026 than in 2025.
- Keyword matching undercounts MCP advisories that never use the term, and our hand judgements are listed in the CSV for checking.
- Download and pull counts include CI systems and mirrors and are not user counts. Docker pulls are cumulative since the image was created.
- The registry sample of 60 gives a rough share, not a precise count.
- This product uses data from the NVD API but is not endorsed or certified by the NVD.
Download the data
- SSRF advisories by month (CSV).
- MCP-related SSRF advisories (CSV): date, IDs, packages, severity, summary.
- Registry servers about web proxies (CSV): name, our label, description.
- SSRF flaws in CISA’s KEV catalog (CSV): all 26 entries with date added, CVE, vendor, product, weakness tags, deadline and ransomware use (21 October 2026).
Cite as: ProxyPicker, “MCP Servers and SSRF”, 17 October 2026, https://proxypicker.com/mcp-server-ssrf/. Data: GitHub Advisory Database (CC BY 4.0), NVD, PyPI, Docker Hub, MCP Registry.
Related: Proxy Bugs in HTTP Libraries · Proxy & AI Gateway CVE Ledger · AI Fetcher IP Ranges.
Press & data requests: email [email protected] for interviews, the raw data behind this page, or corrections. See also our contact page.