PyJWKClient unbounded JWKS endpoint requests via attacker-controlled kid values (DoS)
Published 15 Jun 2026 · Updated 10 Sept 2026
Is your project on an affected pyjwt?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=2.0.0 <2.13.0
- Fixed in
- 2.13.0
pip install 'pyjwt>=2.13.0'Details
> [!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
- DoS against JWKS endpoint (unlimited requests per invalid token)
- DoS against application (network I/O latency)
- Cascading failure (rate limiting clears cache, breaking legitimate auth)
Suggested Fix
1. Add refresh cooldown (refuse refresh more than once per TTL period) 2. Move cache write from finally to else block
Affected Versions
All versions with PyJWKClient (2.4.0 through 2.12.1)
Is GHSA-fhv5-28vv-h8m8 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected pyjwt, and gives you the command that fixes it.
More advisories for pyjwt
- HighGHSA-pxh4-856f-4h89PyJWT: HS256/384/512 verify accepts empty HMAC key via oct JWK (PyJWK/PyJWKClient) enabling token forgery · 22 Oct 2026
- MediumCVE-2026-102275PyJWT accepts inconsistent OKP x/d JWKs, causing public/private key identity confusion · 5 Oct 2026
- MediumCVE-2026-103001PyJWT.decode() reintroduces options-dict mutation, enabling silent claim-verification bypass on dict reuse · 30 Sept 2026
- MediumCVE-2026-101918PyJWT: Unauthenticated RecursionError DoS in pre-verification payload parse (PyJWKClient.get_signing_key_from_jwt / verify_signature=False) · 30 Sept 2026
- MediumCVE-2026-102270PyJWT: ReDoS vulnerability when calling the `is_pem_format` function. · 30 Sept 2026
- HighCVE-2026-102266PyJWT: PyJWK accepts empty HMAC keys, bypassing PyJWT's empty-key validation · 29 Sept 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.