CVE-2026-104120
Received Received - Intake

Server-Side Request Forgery in MCP Server Fetch Tools

Publication date: 2026-10-02

Last updated on: 2026-10-02

Assigner: VulDB

Description
A security vulnerability has been detected in modelcontextprotocol mcp-server-fetch and mcp-server-everything up to 2026.6.4. Affected is the function fetch_url of the file mcp_server_fetch/server.py of the component Fetch Tool. The manipulation of the argument url/path leads to server-side request forgery. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used. The pull request to fix this issue awaits acceptance.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-02
Last Modified
2026-10-02
Generated
2026-10-02
AI Q&A
2026-10-02
EPSS Evaluated
N/A
NVD
CVE-2026-104120
EUVD
EUVD-2026-91161

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
modelcontextprotocol mcp-server-fetch to 2026.6.4 (inc)
modelcontextprotocol mcp-server-everything to 2026.6.4 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Server-Side Request Forgery (SSRF) vulnerability in the mcp-server-fetch and mcp-server-everything components up to version 2026.6.4. The issue is in the fetch_url function of mcp_server_fetch/server.py where manipulating the url or path argument allows an attacker to make unauthorized server-side requests. This could enable access to internal systems or sensitive data.

Detection Guidance

To detect this SSRF vulnerability in mcp-server-fetch or mcp-server-everything, monitor network traffic for unauthorized outbound requests to private IP ranges (127.0.0.1, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), link-local addresses (169.254.0.0/16), or cloud metadata endpoints (169.254.169.254). Check server logs for attempts to access these restricted addresses. Use tools like tcpdump or Wireshark to inspect outgoing connections from the affected servers.

Impact Analysis

An attacker could exploit this to send crafted requests to internal services, bypass network restrictions, or access sensitive data. This may lead to data breaches, unauthorized actions, or further network compromise depending on the server's configuration and exposed services.

Compliance Impact

SSRF vulnerabilities can lead to unauthorized data access, violating GDPR's data protection principles and HIPAA's security requirements for protected health information. Compliance may be compromised if unauthorized access occurs, potentially resulting in legal penalties or reputational damage.

Mitigation Strategies

Immediately update mcp-server-fetch and mcp-server-everything to the latest version that includes SSRF protection. If you cannot update, restrict network access to the server to prevent outbound requests to sensitive addresses. Set the environment variable FETCH_ALLOW_PRIVATE_IPS=0 to enforce SSRF protection. Review and disable any workflows relying on local or private service access.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-104120. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart