Skip to content
Fencer Intel
high —

GHSA-p8g9-xjch-9mxg json

Unknown JWT key IDs each trigger a JWKS fetch in JWTVerifier, amplifying unauthenticated traffic to the identity provider

published 28d ago modified 28d ago

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository PrefectHQ/fastmcp. GitHub has not reviewed it into the GitHub Advisory Database and no CVE record has reached us yet, so everything here comes from the maintainers alone. Read the full advisory on GitHub.

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

Security advisory published by the maintainers of PrefectHQ/fastmcp for fastmcp: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.

Patch / fix

  • pypi fastmcp 3.4.9, 4.1.0

Is GHSA-p8g9-xjch-9mxg in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
pypi fastmcp
>=2.6.0, <3.4.9
>=4.0.0a1, <4.1.0
3.4.9
4.1.0

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of PrefectHQ/fastmcp published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.