FastMCP: direct calls skip authorization after transforms, and M2M OAuth clients can send their secret to a rogue auth server (fixed 3.4.10 / 4.1.2)
Two FastMCP advisories published on 20 October 2026. In 3.0.0–3.4.9 and 4.0.0–4.1.1, a direct tools/call (or resource/prompt lookup) returned a transformed component without re-checking its authorization policy, so a low-privilege client that knows the name could run a tool the policy denies. In 4.0.0–4.1.1, the client-side ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider had no issuer binding, so an untrusted MCP server could point the client at its own authorization server and receive the client secret. Fixed in 3.4.10 and 4.1.2; the OAuth fix also needs you to set issuer=.
What it is
GHSA-7xgj-8392-5q4r (Moderate, 6.8): listing applied transforms and then authorized the final component, but the direct lookup path returned the transformed component without running its AuthCheck. With a transform that changes tags or metadata, a caller without the required scope could invoke an admin tool hidden from the list, or read a protected resource or prompt. Affects fastmcp and fastmcp-slim >= 3.0.0, < 3.4.10 and >= 4.0.0, < 4.1.2.
GHSA-vqqp-x5qm-5qp4 (Moderate, 5.9): the M2M OAuth client wrappers (introduced in 4.0.0a1) did not accept or forward an issuer, so the client trusted whatever authorization server the MCP server advertised and sent client_id and client_secret (or a signed assertion) there. Affects fastmcp and fastmcp-slim >= 4.0.0a1, < 4.1.2; 3.x doesn't have these wrappers.
The 4.1.2 fix adds an issuer parameter to both providers and requires MCP SDK 2.2.0. Upgrading alone is not enough: omitting issuer is still allowed (with an MCPDeprecationWarning).
How to check
- Run `pip show fastmcp fastmcp-slim` and compare with 3.4.10 (3.x) or 4.1.2 (4.x).
- Servers: check whether you use component auth (restrict_tag / AuthCheck) together with tool, provider or session transforms, or proxy templates overlapping protected resources.
- Clients: search your code for ClientCredentialsOAuthProvider or PrivateKeyJWTOAuthProvider, especially where the MCP server URL comes from users or config.
How to fix
- Upgrade to fastmcp / fastmcp-slim 3.4.10 or 4.1.2 or later.
- Pass issuer="https://your-auth-server" to ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider, and rotate client secrets that may have been sent to an untrusted MCP server.
- Until you upgrade, enforce authorization inside the tool handler instead of relying on a policy whose inputs a transform can change.
from fastmcp.client.auth import ClientCredentialsOAuthProvider
auth = ClientCredentialsOAuthProvider(
client_id="my-client-id",
client_secret="my-client-secret",
issuer="https://auth.example.com", # required for protection in 4.1.2+
) Sources
- criticalMalicious npm package @guicai777/mcp-doctor posed as an MCP diagnostic tool and dropped a hidden Windows executable, with a README telling users to run mshta (MAL-2026-20295)
- criticalCVE-2026-77359: Jupyter MCP Server's /api/connect and /api/stop routes skipped the token and Origin checks, so a website or network caller could repoint it to an attacker's Jupyter backend (fixed 1.0.3)
- criticalMalicious npm packages posing as AI SDKs and MCP servers: character-ai-sdk, char-ai-sdk, @mibbp/agent-observer, mrnima-openai-chatgpt-bot and @fdcasj_dfew/md-doc-mcp
- criticalCVE-2026-76807: Doist's official Todoist MCP HTTP server let any website use DNS rebinding to read, create and delete your Todoist data (fixed 10.3.3)