modelcontextprotocol mcp-server-fetch/mcp-server-everything up to 2026.6.4 Fetch Tool server.py fetch_url url/path server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.92+ |
Summary
A vulnerability, which was classified as critical, was found in modelcontextprotocol mcp-server-fetch and mcp-server-everything up to 2026.6.4. Affected by this vulnerability 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 results in server-side request forgery.
This vulnerability is cataloged as CVE-2026-104120. The attack may be launched remotely. Furthermore, there is an exploit available.
The pull request to fix this issue awaits acceptance.
Details
A vulnerability was found in modelcontextprotocol mcp-server-fetch and mcp-server-everything up to 2026.6.4. It has been classified as critical. 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 with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability.
The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-104120. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details and a public exploit are known.
The exploit is shared for download at github.com. It is declared as proof-of-concept. The pull request to fix this issue awaits acceptance.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.9
VulDB Base Score: 7.3
VulDB Temp Score: 6.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Server-side request forgeryCWE: CWE-918
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/01/2026 Advisory disclosed10/01/2026 VulDB entry created
10/01/2026 VulDB entry last update
Sources
Advisory: 4492Status: Confirmed
Confirmation: 🔒
CVE: CVE-2026-104120 (🔒)
GCVE (CVE): GCVE-0-2026-104120
GCVE (VulDB): GCVE-100-412764
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 10/01/2026 20:20Changes: 10/01/2026 20:20 (61)
Complete: 🔍
Submitter: geochen
Cache ID: 216::103
Submit
Accepted
- Submit #960099: https://github.com/modelcontextprotocol/ servers 2026.6.4 Server-Side Request Forgery (by geochen)
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.