UTC
High

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
What it is

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.

What to do

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.

Affected
PackageRegistryAffectedFixed in
mcp-from-openapinpm>= 2.3.0, < 2.5.02.5.0

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.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].