FastMCP flaws before 3.2.0: authenticated SSRF and OAuth confused deputy
Two vulnerabilities were disclosed in PrefectHQ's FastMCP framework prior to version 3.2.0: CVE-2026-32871, where unencoded path parameters in the OpenAPIProvider's RequestDirector allowed path traversal and authenticated SSRF against backend APIs using configured authorization headers, and CVE-2026-27124, where the OAuthProxy failed to validate user consent when handling GitHub authorization codes, creating a confused deputy issue. Both were patched in FastMCP 3.2.0.
Disclosed 2 April 2026 · Record updated 13 September 2026
Impact
An attacker controlling a path parameter could escape the intended API prefix and reach arbitrary backend endpoints with the MCP provider's authorization headers (authenticated SSRF); separately, the OAuthProxy consent flaw could allow authentication bypass via previously authorized GitHub OAuth clients.
Our coverage
No articles linked to this incident yet.
Sources
- nvd.nist.govhttps://nvd.nist.gov/vuln/detail/CVE-2026-32871
- nvd.nist.govhttps://nvd.nist.gov/vuln/detail/CVE-2026-27124
