PyJWT: PyJWKClient still amplifies unauthenticated JWKS fetches on unknown kid values (incomplete fix of CVE-2026-48524)

Why this deserves its current priority

CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps jpadilla/pyjwt (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for jpadilla/pyjwt.
2. 2Review the reported fix. Update jpadilla/pyjwt to 2.14.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Sep 28, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 28, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 28, 2026

Sources and claim methodology

• GitHub security advisorygithub.com
• GitHub security advisorygithub.com
• GitHub security advisorygithub.com

Related CVEs

• PyJWT: Unauthenticated RecursionError DoS in pre-verification payload parse (PyJWKClient.get_signing_key_from_jwt / verify_signature=False)Same jpadilla/pyjwt package
• PyJWT: Uncaught RecursionError in jwt.decode() on deeply nested token headerSame jpadilla/pyjwt package
• PyJWK accepts empty HMAC keys, bypassing PyJWT's empty-key validationSame jpadilla/pyjwt package
• PyJWT: PyJWKClient follows redirects when fetching JWKSSame jpadilla/pyjwt package
• PyJWT: Asymmetric-PEM detection bypass: whitespace/line-ending-mutated public keys skip the HS/asymmetric confusion guardSame jpadilla/pyjwt package
• PyJWT: Non-canonical signature segments enable raw-token revocation bypassSame jpadilla/pyjwt package