# CVE-2026-51994: Server-side request forgery in n/a

> An attacker can exploit SSRF in mcp-remote by manipulating the resource_metadata URL in a remote MCP server's WWW-Authenticate header.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 24 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-8rrr-xx35-4q6h

## What is CVE-2026-51994?

CVE-2026-51994 is a critical server-side request forgery vulnerability in n/a, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

mcp-remote versions 0.1.32 through 0.1.38 are vulnerable to Server-Side Request Forgery (SSRF) via the resource_metadata URL extracted from a remote MCP server's WWW-Authenticate header

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

## Which versions are affected by CVE-2026-51994?


## How do I fix CVE-2026-51994?

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

## Is CVE-2026-51994 being exploited?

There is no known exploitation of CVE-2026-51994 in the wild and no public exploit code.

Public exploit code:

- Forensic audit of mcp-remote: seven OAuth trust-boundary advisories, five CVE records (CVE-2026-51994/51995/51996/51997/52001). Server-selected request path (CWE-918) run against loopback canaries in 62 stable releases, 0.1.32 to the current 0.15.1; selected code and namespace signatures under 12 other npm names; search blind spots above 350 KiB. (github_poc): https://github.com/playb0t/mcp-remote-oauth-security

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-51994 and fix it if it is affected.

What it is: CVE-2026-51994 is a critical server-side request forgery vulnerability in n/a, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-51994 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2026-51994/ (Markdown: https://insights.sbomify.com/CVE-2026-51994/index.md)
```

## Sources

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

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