Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-104120 high CVSS 7.3

SSRF (Server-Side Request Forgery) in modelcontextprotocol mcp-server-fetch and mcp (CVE-2026-104120)

Summary

SSRF in modelcontextprotocol mcp-server-fetch and mcp (CVE-2026-104120). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-104120 has been found in modelcontextprotocol mcp-server-fetch and mcp.
Risk of unauthorized operations or information disclosure. CVSS score: 7.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "modelcontextprotocol mcp-server-fetch and mcp CVE-2026-104120" on the vendor's site.

CVE-2026-104120 (modelcontextprotocol mcp-server-fetch and mcp) — CWE-918 / CVSS v3 7.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SSRF (CWE-918) exists in modelcontextprotocol mcp-server-fetch and mcp.

📍 Affected scope

Check the vendor advisory for the affected versions of modelcontextprotocol mcp-server-fetch and mcp.

🔥 Severity

Severity: High (CVSS 7.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで modelcontextprotocol mcp-server-fetch and mcp を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details