FastMCP advisories: authorization skipped after transforms
GitHub published two medium-severity FastMCP advisories on 23 Oct 2026. GHSA-7xgj-8392-5q4r says a server transform could change what an authorization policy checks, so direct calls skipped the policy. GHSA-vqqp-x5qm-5qp4 covers client wrappers that built OAuth providers without issuer binding. Fixes: 3.4.10 and 4.1.2.
Facts read on .
The maintainers' assessment of the first advisory says direct lookups checked the original component but returned the transformed one without rechecking its policy. A client that knows a component identifier could call a tool, or read a resource or prompt, that the configured policy denies. It affects fastmcp and fastmcp-slim 3.0.0 through 3.4.9 and 4.0.0 through 4.1.1 when component authorization is combined with transforms or with protected resources that overlap proxy templates.
The fixes authorize the final transformed components. Until upgrading, the advisory suggests avoiding overlapping proxy templates for protected resources and enforcing authorization at the handler or server boundary rather than in a policy whose inputs a transform changes.
The second advisory affects fastmcp and fastmcp-slim 4.0.0 through 4.1.1. The maintainers say an untrusted or compromised MCP server could advertise a different authorization server and receive the client secret or a signed assertion; 4.1.2 adds an issuer setting and requires MCP SDK 2.2.0. It echoes the TypeScript SDK issuer-binding advisory from 6 Oct 2026.
Sources
- GHSA-7xgj-8392-5q4r: FastMCP post-transform authorization (github.com), read
- GHSA-vqqp-x5qm-5qp4: FastMCP client OAuth issuer binding (github.com), read