Quick answers
- Is CVE-2025-69196 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-69196 being exploited in the wild.
- How severe is CVE-2025-69196?
- Medium severity, with a CVSS score of 6.5, published 16 March 2026.
- Which products and versions are affected?
- fastmcp (PyPI) ECOSYSTEM:introduced=0,fixed=2.14.2; Red Hat Developer Hub 1.
- Is there a fix for CVE-2025-69196?
- Yes. fastmcp (PyPI): upgrade to 2.14.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-69196 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-69196?
- Check whether you run fastmcp (PyPI) or Red Hat Developer Hub at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- fastmcp (PyPI): upgrade to 2.14.2 or later
pip install "fastmcp>=2.14.2"
Technical details
A vulnerability exists in the FastMCP OAuth Proxy where the server fails to properly validate the 'resource' parameter during authorization and token requests. Instead of issuing a scoped token for a specific MCP server, the system issues a generic token for the base URL. An attacker can exploit this by hosting a malicious MCP server that points to a legitimate OAuth Proxy; when a victim authenticates, the attacker can capture the resulting token and reuse it to access other legitimate MCP servers sharing the same authorization server. This violates the Resource Indicators OAuth extension specification. The issue is fixed in version 2.14.2.
Affected products
- PrefectHQ FastMCP < 2.14.2
- Red Hat Red Hat Satellite 6 6
- Red Hat Red Hat Developer Hub 1
- Red Hat Red Hat OpenShift AI (RHOAI)
Identifiers
- CVE-2025-69196
- GHSA-5h2m-4q8j-pqpj
- PYSEC-2026-2474
Timeline
- 2026-03-15: advisory: GitHub advisory published by maintainer
- 2026-03-16: disclosed: CVE published to NVD
- 2026-03-16: patched: Fix released in version 2.14.2