# CVE-2025-65513: Fetch MCP Server has a Server-Side Request Forgery (SSRF) vulnerability

> Attackers can bypass private IP validation to access internal network resources via Server-Side Request Forgery in the fetch-mcp library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Dec 2025
- **Updated:** 11 Dec 2025
- **Also known as:** GHSA-8fxj-2g9q-8fjw

## What is CVE-2025-65513?

CVE-2025-65513 is a high-severity server-side request forgery vulnerability in n/a, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

fetch-mcp v1.0.2 and before is vulnerable to Server-Side Request Forgery (SSRF) vulnerability, which allows attackers to bypass private IP validation and access internal network resources.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2025-65513?

2 open source packages ship an affected version, including mcp-fetch-server. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mcp-fetch-server` | npm | All versions to 1.0.2 | None |
| `mcp-fetch-server` | npm | All versions to 1.0.2 | None |

Products: Zcaceres Fetch Mcp Server.

## How do I fix CVE-2025-65513?

No fix has been published for CVE-2025-65513 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-65513 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65513 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-65513 and fix it if it is affected.

What it is: CVE-2025-65513 is a high-severity server-side request forgery vulnerability in n/a, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65513 exists.

Affected packages and fixed versions:
- mcp-fetch-server (npm): affected all versions up to 1.0.2; no fix listed
- mcp-fetch-server (npm): affected all versions up to 1.0.2; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-65513/ (Markdown: https://insights.sbomify.com/CVE-2025-65513/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-65513
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-65513
- OSV: https://osv.dev/vulnerability/CVE-2025-65513

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-65513/
Summaries are generated and may contain mistakes; the official description above is the record.