Skip to main content
VulnerabilityPublished Updated

CVE-2025-69196: jlowin fastmcp · Incorrect Authorization

Affects jlowin fastmcpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.4 High : upgrade to 2.14.2 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
7.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.14.2
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade fastmcp and jlowin/fastmcp to 2.14.2.

Affected software

ProductAffectedFixed in
jlowinfastmcpAffected
  • <2.14.2
Fixed in
  • 2.14.2
GitHubjlowin/fastmcppkg:github/jlowin/fastmcpOther threatsAffected
  • <2.14.2
Fixed in
  • 2.14.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade fastmcp to version 2.14.2 or later, where this authorization issue has been fixed. No other mitigation is indicated by the vendor advisory. Patch status is confirmed by Red Hat advisory.

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.

References

Community reviews

Loading reviews…