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
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…
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.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| fastmcp | PyPI | >= 4.0.0a1, < 4.1.2 | 4.1.2 |
| fastmcp-slim | PyPI | >= 4.0.0a1, < 4.1.2 | 4.1.2 |
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
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- CriticalFastMCP OpenAPI Provider has an SSRF & Path Traversal Vulnerabilityfastmcp
- HighFastMCP: Missing Consent Verification in OAuth Proxy Callback Facilitates Confused Deputy Vulnerabilitiesfastmcp
- HighFastMCP OAuth Proxy token reuse across MCP serversfastmcp
- HighFastMCP updated to MCP 1.23+ due to CVE-2025-66416fastmcp
- HighFastMCP Auth Integration Allows for Confused Deputy Account Takeoverfastmcp
- MediumFastMCP: Post-transform component authorization is skipped on direct callsfastmcp, fastmcp, fastmcp-slim, fastmcp-slim
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.