UTC
Medium

FastMCP MCP client wrappers construct M2M OAuth providers without issuer binding — client secret redirectable to attacker-advertised authori

GHSA-vqqp-x5qm-5qp4 · published 2026-10-23

Severity
Medium
CVSS score
5.9
Chance of exploitation (EPSS)
No CVE
Fixed in
4.1.2
What it is

Severity: Medium-High Any application using fastmcp's M2M OAuth providers (ClientCredentialsOAuthProvider, PrivateKeyJWTOAuthProvider) to connect to user-supplied or untrusted MCP server URLs is vulnerable to credential disclosure and client impersonation. Affected parties: Prefect Cloud users running agents with fastmcp that connect to user-provided MCP servers Any deployment using fastmcp's M2M auth to connect to MCP servers where the URL is attacker-controllable or the server is compromised Attack scenarios: User misconfigures MCP server URL in Prefect agent config MCP server URL obtained from user input without validation Legitimate MCP server is compromised/redirected MCP service provid…

What to do

Upgrade fastmcp to 4.1.2 or later, and fastmcp-slim to 4.1.2 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.

This report is accepted as a FastMCP credential-binding vulnerability. Affected versions of the OAuth client credentials providers do not expose the authorization-server issuer that owns pre-registered credentials. An untrusted or compromised MCP server can therefore advertise a different authorization server and receive the client secret or a signed assertion. Signing keys themselves remain local; assertion replayability depends on the assertion source and audience policy. Affected stable versions are 4.0.0–4.1.1 of fastmcp and fastmcp-slim. The wrappers were introduced in 4.0.0a1; 3.x does not include them.

Affected
PackageRegistryAffectedFixed in
fastmcpPyPI>= 4.0.0a1, < 4.1.24.1.2
fastmcp-slimPyPI>= 4.0.0a1, < 4.1.24.1.2
Downstream in the Official MCP Registry

9 registered MCP servers install an affected version today, by the dependency versions a fresh install resolves.

  • io.github.bchoi-qwe/aeso-mcpfastmcp@4.0.0b3
  • io.github.ClickHouse/mcp-clickhousefastmcp@4.0.11
  • io.github.docdyhr/macwhisper-mcp-serverfastmcp@4.1.0
  • io.github.palewire/datawrapper-mcpfastmcp@4.0.3
  • io.github.RichieB2B/supersaas-slots-mcpfastmcp@4.0.10
  • io.github.Sendmux/sendmux-mcpfastmcp@4.0.3
  • io.github.seothief/insurance-claim-mcpfastmcp@4.1.0
  • io.github.simonether/kwork-mcpfastmcp@4.0.10
  • io.github.startreedata/mcp-pinotfastmcp@4.1.0
See the trace →

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].