Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.1
CVE-2026-51994: mcp-remote 0.1.32‑0.1.38 lets attackers trigger unauthorized network requests
CVE-2026-51994 · published 1 month ago
Summary
Versions 0.1.32 through 0.1.38 of the mcp-remote tool can be tricked into contacting any address specified in a server’s authentication header. This could let a malicious server cause your system to connect to internal services or external sites without permission, potentially exposing data or services. Upgrade to a newer, patched version of mcp-remote or apply the vendor’s recommended configuration changes to block the unsafe request handling.
Original advisory text
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
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
References
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/51xxx/CVE-2026-51994... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-51994 Vendor Advisory
- https://github.com/geelen/mcp-remote Product
- https://github.com/geelen/mcp-remote/security/advisories Vendor Advisory
- https://github.com/playb0t/mcp-remote-oauth-security/blob/v1.0.1/advisories/F-01... Vendor Advisory
- https://github.com/playb0t/mcp-remote-oauth-security#readme Product
Internet-facing
3 days
Internal
60 days
- Not known to be exploited
- Can be exploited automatically
- Gives an attacker full control
Severity
9.1
Critical
Type
CWE-918Server-Side Request Forgery (SSRF)
Timeline
Published24 Sep 2026
Updated24 Oct 2026
First seen24 Sep 2026
Track software like this
Free during beta