Fetch MCP Server has a Server-Side Request Forgery (SSRF) vulnerability
CVE-2025-65513 · GHSA-8fxj-2g9q-8fjw · published 2025-12-10
- Severity
- Medium
- CVSS score
- 6.3
- Chance of exploitation (EPSS)
- 0.48%
- Fixed in
- No fix yet
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Partial
- CISA SSVC
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.
No fixed release is listed yet for mcp-fetch-server. Follow the source advisory for updates, and until one ships:
General guidance from ShieldPi, not a vendor fix
- Server-side request forgery. Restrict its outbound network access to the hosts it needs, and keep internal addresses and cloud metadata endpoints out of its reach.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| mcp-fetch-server | npm | <= 1.0.2 | No fix yet |
- CriticalMLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebindingmlflowExploited
- Critical@zereight/mcp-gitlab Vulnerable to Server-Side Request Forgery@zereight/mcp-gitlab
- CriticalSSRF + LLM API key exfiltration via user-controlled basepath / baseUrl in 8 chat-model nodesflowise, flowise-components
- CriticalLocalAI POST /models/apply permits unauthenticated server-side request forgery through gallery URLsgithub.com/mudler/LocalAI
- CriticalFastMCP OpenAPI Provider has an SSRF & Path Traversal Vulnerabilityfastmcp
- CriticalBentoML SSRF Vulnerability in File Upload Processingbentoml
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.