Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
PyJWK Client in the pyjwt package, versions 2.0.0 up to but not including 2.13.0, makes a fresh request to the JWKS endpoint for each token carrying an unknown key ID, with no rate limit. An attacker can send such tokens to trigger many outbound requests, but the impact depends on how the JWKS endpoint responds, and the source says it reduces authentication availability until the next successful fetch rather than causing full denial of service. Upgrade pyjwt to version 2.13.0 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 3.7 | Low | 3.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0040, the 34th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:29 UTC First seen by agentprime
- 31 Oct 2026, 14:29 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-fhv5-28vv-h8m8
- OSV: GHSA-fhv5-28vv-h8m8
- github.com/jpadilla/pyjwt/security/advisories/GHSA-fhv5-28vv-h8m8
- nvd.nist.gov/vuln/detail/CVE-2026-48524
- github.com/github/advisory-database/pull/8522
- github.com/jpadilla/pyjwt
- github.com/pypa/advisory-database/tree/main/vulns/pyjwt/PYSEC-2026-177.yaml