FastMCP: Missing Consent Verification in OAuth Proxy Callback Facilitates Confused Deputy Vulnerabilities
CVE-2026-27124 · GHSA-rww4-4w9c-7733 · published 2026-03-31 · updated 2026-04-06
- Severity
- High
- CVSS score
- 8.2
- Chance of exploitation (EPSS)
- 0.21%
- Fixed in
- 3.2.0
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Partial
- CISA SSVC
While testing the GitHubProvider OAuth integration, which allows authentication to a FastMCP MCP server via a FastMCP OAuthProxy using GitHub OAuth, it was discovered that the FastMCP OAuthProxy does not properly validate the user's consent upon receiving the authorization code from GitHub. In combination with GitHub’s behavior of skipping the consent page for previously authorized clients, this introduces a Confused Deputy vulnerability.
Upgrade fastmcp to 3.2.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.
To mitigate this issue, the OAuthProxy should verify that the browser sending the authorization code has actually given consent for the corresponding client. This can be achieved by setting and validating a consent cookie or similar browser-bound state, as described in the mitigations section for this vulnerability in the MCP specification.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| fastmcp | PyPI | < 3.2.0 | 3.2.0 |
47 registered MCP servers install an affected version today, by the dependency versions a fresh install resolves.
- aws.api.us-east-1.ecs-mcp/serverfastmcp@2.14.0
- aws.api.us-east-1.eks-mcp/serverfastmcp@2.14.0
- io.github.aadeshrao123/unreal-mcpfastmcp@2.14.7
- io.github.aahl/mcp-aktoolsfastmcp@2.14.7
- io.github.aahl/mcp-notifyfastmcp@2.14.7
- io.github.aahl/mcp-vodsfastmcp@2.14.7
- io.github.ai-mcpower/mcpower-proxyfastmcp@2.13.0.2
- io.github.alex-feel/mcp-context-serverfastmcp@3.1.0
- io.github.ameyxd/petromcpfastmcp@2.14.7
- io.github.andreasd083/amazing-marvin-complete-mcpfastmcp@2.14.7
- io.github.ariffazil/arifos-mcpfastmcp@3.0.1
- io.github.aws/aws-mcpfastmcp@2.14.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
- CriticalBentoML SSRF Vulnerability in File Upload Processingbentoml
- Criticallobe-chat `/api/proxy` endpoint Server-Side Request Forgery vulnerability@lobehub/chat
- CriticalFastMCP OpenAPI Provider has an SSRF & Path Traversal Vulnerabilityfastmcp
- 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
- MediumFastMCP MCP client wrappers construct M2M OAuth providers without issuer binding — client secret redirectable to attacker-advertised authorifastmcp, 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.