PyJWT: PyJWKClient still amplifies unauthenticated JWKS fetches on unknown kid values (incomplete fix of CVE-2026-48524) — GHSA-2GX3-RCP4-G85Q
GitHub · GitHub · GHSA-2GX3-RCP4-G85Q
ID
GHSA-2GX3-RCP4-G85Q
GHSA-2GX3-RCP4-G85Q
Date
Source
GitHub
GitHub
Vendor
GitHub
GitHub
Threat
medium
medium
CVSS
5.3
5.3
EPSS
0.00354
0.00354
Summary
Summary CVE-2026-48524 (GHSA-fhv5-28vv-h8m8, "PyJWKClient unbounded JWKS endpoint requests via attacker-controlled kid values (DoS)") was fixed in 2.13.0 by stopping fetch_data() from clearing the cache on a fetch error. That closed one amplification path but did not add the mitigation the advisory's title implies: there is still no rate-limit, negative-cache, or minimum-refresh-interval for unknown kids. At HEAD,…
Timeline
- Published by source
- 2026-09-29
Risk context
- Reported severity or threat level: medium.
- Reported CVSS score: 5.3 out of 10.
- Reported EPSS value: 0.00354.
- Review exposure for the affected product or family: pip: pyjwt.
Product
pip: pyjwt
What to do
General, cautious steps (verify details in the official source):
- Review exposure and plan remediation based on risk and environment.
- Identify affected product versions in your inventory and verify whether you are impacted.
- Apply vendor patches/updates or recommended mitigations as soon as available.
- Read the official advisory for exact affected versions and remediation steps.
Official advisory
Evidence and provenance
- Canonical advisory ID
- GHSA-2GX3-RCP4-G85Q
- Source
- GitHub
- Vendor
- GitHub
- Published by source
- 2026-09-29
- Last source activity
- 2026-09-29
- Additional identifiers
- CVE-2026-101917
- Curated by
- hlukh.ch
Related advisories and connections
These advisories are connected by shared CVE, product, vendor, source, or time signals.