pyjwt
Affected
- introduced
2.0.0, fixed2.13.0(ecosystem)
Fixed versions
2.13.0
Fix
- Fixed version
2.13.0pip install --upgrade pyjwt==2.13.0
Advisory
Also known as: CVE-2026-48524, PYSEC-2026-177
PyJWKClient unbounded JWKS endpoint requests via attacker-controlled kid values (DoS)
> [!NOTE]
> The vulnerability surfaces only when a JWKS fetch fails; an attacker can attempt to provoke that with sustained unknown-kid traffic, but the outcome depends on upstream JWKS-endpoint behavior (rate limiting, transient errors) which is beyond the attacker's control. Impact is reduced auth availability until the next successful fetch, not complete denial of service.
Summary
PyJWKClient.get_signing_key() forces a fresh HTTP request to the JWKS endpoint for every JWT with an unknown kid value, with no rate limiting. Since kid comes from the unverified token header, an attacker can trigger unlimited outbound requests.
Additionally, fetch_data() finally block clears the JWKS cache on network error.
Root Cause
jwt/jwks_client.py:172-198 - get_signing_key(kid) calls get_signing_keys(refresh=True) for unknown kids, bypassing TTL cache with no cooldown.
jwt/jwks_client.py:120-122 - finally block writes None to cache on error, clearing valid data.
Impact
Suggested Fix
Affected Versions
All versions with PyJWKClient (2.4.0 through 2.12.1)
Low Basis: The source's own band: LOW
2.0.0, fixed 2.13.0 (ecosystem)2.13.0
2.13.0pip install --upgrade pyjwt==2.13.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0