UTC
High

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

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.

What to do

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.

If you cannot upgrade yet

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.

Affected
PackageRegistryAffectedFixed in
fastmcpPyPI< 3.2.03.2.0
Downstream in the Official MCP Registry

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
All 47 servers on 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].