CVE-2025-69196

MEDIUMNVD 6.56.5
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: nvd
Trending — 3 sources updated this weekElevated
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
6.5(low)
EPSS
27.9%
KEV
Not listed

Published

March 16, 2026

Last Modified

July 8, 2026

Advisory Details (5)

Auto-updated Jul 8, 2026
🔬 Proof of concept available. Patch available. Sources: github, redhat.
redhat

2448179 – (CVE-2025-69196) CVE-2025-69196 fastmcp: FastMCP: Improper token issuance due to incorrect resource parameter handling

https://bugzilla.redhat.com/show_bug.cgi?id=2448179
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2025-69196
github Patch Available🟡 PoC Available

Improper Resource Handling in FastMCP OAuth Proxy Enables Token Reuse Across MCP Servers · Advisory · PrefectHQ/fastmcp · GitHub

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

Vendor Advisories for CVE-2025-69196(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
fastmcp0.1.0 ... 2.9.2 (75 versions)2.14.2

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 18× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-09 19:10 UTCEPSS rescore
  4. 2026-07-08 15:15 UTCEPSS rescore
  5. 2026-07-08 14:36 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  6. 2026-07-08 12:47 UTCMITRE cvelistV5CVSS v3 → 7.4 · severity → HIGH
  7. 2026-07-07 13:46 UTCEPSS rescore
  8. 2026-07-06 16:27 UTCEPSS rescore
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-05 02:30 UTCEPSS rescore
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-01 15:06 UTCEPSS rescore
  15. 2026-06-30 23:22 UTCEPSS rescore
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-30 04:33 UTCEG score recompute
  18. 2026-06-30 04:31 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2025-69196?
CVE-2025-69196 is a medium vulnerability published on March 16, 2026. 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…
When was CVE-2025-69196 disclosed?
CVE-2025-69196 was first published in the National Vulnerability Database on March 16, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-69196 actively exploited?
CVE-2025-69196 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-69196?
CVE-2025-69196 has a CVSS v3 base score of 6.5 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2025-69196?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-69196, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-69196

Explore →

Is Your Infrastructure Affected by CVE-2025-69196?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.