FrontMCP and mcp-from-openapi have bypass of OpenAPI external $ref SSRF fix
CVE-2026-59973 · GHSA-65h7-9wrw-629c · published 2026-09-11
- Severity
- High
- CVSS score
- 8.5
- Chance of exploitation (EPSS)
- 0.39%
- Fixed in
- 2.5.0
- Exploitation Public proof of concept
- Automatable No
- Technical impact Partial
- CISA SSVC
The previous advisory documented SSRF during untrusted OpenAPI $ref dereferencing. The latest patched version still lets an attacker trigger backend-origin requests to loopback or private network services through equivalent URL forms. In hosted or multi-user FrontMCP deployments where users can import or configure OpenAPI specs, this can expose internal admin APIs, metadata-like services, and other network endpoints that external users cannot reach directly. The impact depends on whether a deployment treats OpenAPI adapter configuration as trusted administrator-only input. If untrusted authenticated users can import specs, this is a high-impact SSRF fix bypass.
Upgrade mcp-from-openapi to 2.5.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
1. Do not rely on parsed hostname denylist checks for external $ref URLs. 2. Resolve hostnames before the request and reject loopback, private, link-local, multicast, unspecified, and metadata ranges. 3. Normalize IPv4-mapped IPv6 before range checks. 4. Revalidate every redirect target before following it, or disable redirects during external $ref dereferencing. 5. Pin the validated IP to the actual request with a custom dispatcher, lookup hook, or equivalent connect-time control. 6. Apply the same protected client to fromURL() initial spec loads. 7. Consider disabling external refs by default for untrusted OpenAPI specs and requiring explicit allowlists. 8.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| mcp-from-openapi | npm | >= 2.3.0, < 2.5.0 | 2.5.0 |
- 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.