Is CVE-2026-104120 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-104120 being exploited in the wild.

How severe is CVE-2026-104120?

High severity, with a CVSS score of 7.3, published 2 October 2026.

Which products and versions are affected?

Modelcontextprotocol Mcp-Server-Everything up to 2026.6.4; Modelcontextprotocol Mcp-Server-Fetch up to 2026.6.4.

Is there a fix for CVE-2026-104120?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-104120 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-104120?

Check whether you run Modelcontextprotocol Mcp-Server-Everything or Modelcontextprotocol Mcp-Server-Fetch at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-104120: Model Context Protocol mcp-server-fetch SSRF in fetch_url

CVE-2026-104120 · Severity: high · CVSS 7.3 · Published 2026-10-02

Model Context Protocol's mcp-server-fetch is a tool that fetches content from URLs on behalf of applications and AI systems. A vulnerability in the fetch_url function allows an attacker to request arbitrary URLs or cloud metadata endpoints by manipulating the URL parameter, potentially exposing sensitive internal data or credentials. An attacker with network access can exploit this remotely without authentication.

Vendors: Modelcontextprotocol.

Quick answers

Is CVE-2026-104120 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-104120 being exploited in the wild.
How severe is CVE-2026-104120?: High severity, with a CVSS score of 7.3, published 2 October 2026.
Which products and versions are affected?: Modelcontextprotocol Mcp-Server-Everything up to 2026.6.4; Modelcontextprotocol Mcp-Server-Fetch up to 2026.6.4.
Is there a fix for CVE-2026-104120?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-104120 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-104120?: Check whether you run Modelcontextprotocol Mcp-Server-Everything or Modelcontextprotocol Mcp-Server-Fetch at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a server-side request forgery (SSRF) in the fetch_url function of mcp_server_fetch/server.py, where insufficient validation of the url/path argument allows an attacker to request private IP addresses and cloud metadata services. The attack vector is network-based with no authentication required. A fix exists in pull request #4890 that guards against private-IP and cloud metadata SSRF.

Affected products

modelcontextprotocol mcp-server-fetch up to 2026.6.4
modelcontextprotocol mcp-server-everything up to 2026.6.4

Timeline

2026-06-05: disclosed: Security advisory submitted
2026-10-02: advisory: CVE-2026-104120 published
2026-09-28: other: Pull request #4890 submitted for fix

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.