CVE-2025-69196

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 71% of all CVEs by exploit prediction. 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: epss, nvd
Elevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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(medium)
EG Risk
45(Track)
EG Risk 45/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

March 16, 2026

Last Modified

July 15, 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.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatsatellite/foreman-mcp-server-rhel9:17827393442026-07-07redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

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 6× in last 7d / 47× 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-08-25 13:48 UTCEPSS rescore
  2. 2026-08-24 14:16 UTCEPSS rescore
  3. 2026-08-23 00:18 UTCEPSS rescore
  4. 2026-08-21 23:48 UTCEPSS rescore
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 13:46 UTCEPSS rescore
  9. 2026-08-16 14:55 UTCEPSS rescore
  10. 2026-08-16 11:23 UTCEG score recompute
  11. 2026-08-16 11:23 UTCVendor advisory
  12. 2026-08-16 02:14 UTCEPSS rescore
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 07:29 UTCEG score recompute
  15. 2026-08-14 07:29 UTCVendor advisory
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-12 22:45 UTCEG score recompute
  18. 2026-08-12 22:45 UTCVendor advisory
  19. 2026-08-12 13:50 UTCEPSS rescore
  20. 2026-08-11 21:34 UTCEG score recompute
  21. 2026-08-11 21:34 UTCVendor advisory
  22. 2026-08-11 13:42 UTCEPSS rescore
  23. 2026-08-10 23:59 UTCEPSS rescore
  24. 2026-08-10 08:18 UTCEG score recompute
  25. 2026-08-10 08:18 UTCVendor advisory
Show 69 more
  1. 2026-08-09 13:46 UTCEPSS rescore
  2. 2026-08-09 07:05 UTCEG score recompute
  3. 2026-08-09 07:05 UTCVendor advisory
  4. 2026-08-08 16:36 UTCEPSS rescore
  5. 2026-08-07 17:43 UTCEG score recompute
  6. 2026-08-07 17:43 UTCVendor advisory
  7. 2026-08-07 16:27 UTCEPSS rescore
  8. 2026-08-06 13:46 UTCEPSS rescore
  9. 2026-08-06 01:44 UTCEG score recompute
  10. 2026-08-06 01:44 UTCVendor advisory
  11. 2026-08-05 19:17 UTCEPSS rescore
  12. 2026-08-04 10:37 UTCEPSS rescore
  13. 2026-08-04 00:55 UTCEG score recompute
  14. 2026-08-04 00:55 UTCVendor advisory
  15. 2026-08-03 10:35 UTCEPSS rescore
  16. 2026-08-02 16:53 UTCEG score recompute
  17. 2026-08-02 16:53 UTCVendor advisory
  18. 2026-08-02 02:26 UTCEPSS rescore
  19. 2026-08-01 04:15 UTCEPSS rescore
  20. 2026-07-30 16:27 UTCEPSS rescore
  21. 2026-07-30 01:30 UTCEPSS rescore
  22. 2026-07-27 14:13 UTCEPSS rescore
  23. 2026-07-26 14:54 UTCEPSS rescore
  24. 2026-07-26 14:54 UTCEPSS rescore
  25. 2026-07-25 14:17 UTCEPSS rescore
  26. 2026-07-25 14:17 UTCEPSS rescore
  27. 2026-07-24 14:17 UTCEPSS rescore
  28. 2026-07-23 14:18 UTCEPSS rescore
  29. 2026-07-23 14:18 UTCEPSS rescore
  30. 2026-07-23 03:02 UTCEG score recompute
  31. 2026-07-22 14:08 UTCEPSS rescore
  32. 2026-07-21 15:24 UTCEPSS rescore
  33. 2026-07-20 17:08 UTCEPSS rescore
  34. 2026-07-19 14:30 UTCEPSS rescore
  35. 2026-07-19 14:30 UTCEPSS rescore
  36. 2026-07-19 02:28 UTCEPSS rescore
  37. 2026-07-19 02:28 UTCEPSS rescore
  38. 2026-07-18 10:04 UTCEPSS rescore
  39. 2026-07-18 10:04 UTCEPSS rescore
  40. 2026-07-18 06:59 UTCOSV refresh
  41. 2026-07-16 17:02 UTCEPSS rescore
  42. 2026-07-16 17:02 UTCEPSS rescore
  43. 2026-07-15 16:57 UTCEPSS rescore
  44. 2026-07-15 16:57 UTCEPSS rescore
  45. 2026-07-15 02:22 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  46. 2026-07-15 02:06 UTCMITRE cvelistV5CVSS v3 → 7.4 · severity → HIGH
  47. 2026-07-15 02:00 UTCEPSS rescore
  48. 2026-07-15 01:59 UTCEPSS rescore
  49. 2026-07-13 06:12 UTCEPSS rescore
  50. 2026-07-12 05:46 UTCEPSS rescore
  51. 2026-07-12 05:46 UTCEPSS rescore
  52. 2026-07-11 08:27 UTCEPSS rescore
  53. 2026-07-11 08:27 UTCEPSS rescore
  54. 2026-07-09 19:10 UTCEPSS rescore
  55. 2026-07-08 15:15 UTCEPSS rescore
  56. 2026-07-08 14:36 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  57. 2026-07-08 12:47 UTCMITRE cvelistV5CVSS v3 → 7.4 · severity → HIGH
  58. 2026-07-07 13:46 UTCEPSS rescore
  59. 2026-07-06 16:27 UTCEPSS rescore
  60. 2026-07-06 02:23 UTCEPSS rescore
  61. 2026-07-05 02:30 UTCEPSS rescore
  62. 2026-07-05 02:30 UTCEPSS rescore
  63. 2026-07-04 06:31 UTCEPSS rescore
  64. 2026-07-04 06:31 UTCEPSS rescore
  65. 2026-07-01 15:06 UTCEPSS rescore
  66. 2026-06-30 23:22 UTCEPSS rescore
  67. 2026-06-30 23:22 UTCEPSS rescore
  68. 2026-06-30 04:33 UTCEG score recompute
  69. 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 15, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 71.5% of all scored CVEs.
What is the CVSS score of CVE-2025-69196?
CVE-2025-69196 has a CVSS v3 base score of 6.5 (NVD).
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.