Authentication disruption via unbounded JWKS refreshes
Published May 28, 2026 · Updated May 28, 2026
Denial of service in PyJWKClient in PyJWT before 2.13.0 allows remote attackers to disrupt authentication via crafted JWT key IDs. The get_signing_key() path refreshes the JWKS for every unknown unverified kid without rate limiting, and fetch_data() clears cached keys after a request failure. Exploitation requires a failed JWKS fetch, so upstream throttling or transient errors determine whether sustained traffic reduces authentication availability.
Summary
What happened
Denial of service in PyJWKClient in PyJWT before 2.13.0 allows remote attackers to disrupt authentication via crafted JWT key IDs. The get_signing_key() path refreshes the JWKS for every unknown unverified kid without rate limiting, and fetch_data() clears cached keys after a request failure. Exploitation requires a failed JWKS fetch, so upstream throttling or transient errors determine whether sustained traffic reduces authentication availability.
The record
- CVE
- CVE-2026-48524
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- Jose Padilla
- Product
- PyJWT
- Classifications
- CWE-755, CWE-460, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.13.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo