Is pyjwt 2.13 vulnerable?
PyPI · 1 release from 2.13.0 to 2.13.0 · latest pyjwt is 2.15.1 · checked 18 Nov 2026
Yes: 15 known advisories
Yes. pyjwt 2.13.0, the last 2.13 release, is affected by 15 known security advisories (1 critical, 6 high, 8 medium), including CVE-2026-102268, CVE-2026-102266, CVE-2026-102273. At least one has no fixed release yet.
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
Advisories affecting pyjwt 2.13.0
PyJWT: HS256/384/512 verify accepts empty HMAC key via oct JWK (PyJWK/PyJWKClient) enabling token forgery
- Affected
- <2.14.0
- Fixed in
- 2.14.0
PyJWT accepts inconsistent OKP x/d JWKs, causing public/private key identity confusion
- Affected
- >=2.1.0 <2.15.0
- Fixed in
- 2.15.0
PyJWT.decode() reintroduces options-dict mutation, enabling silent claim-verification bypass on dict reuse
- Affected
- >=2.11.0 <=2.13.0
- Fixed in
- No fix released
PyJWT: Unauthenticated RecursionError DoS in pre-verification payload parse (PyJWKClient.get_signing_key_from_jwt / verify_signature=False)
- Affected
- >=2.0.0a1 <2.15.0
- Fixed in
- 2.15.0
PyJWT: ReDoS vulnerability when calling the `is_pem_format` function.
- Affected
- <2.14.0
- Fixed in
- 2.14.0
PyJWT: PyJWK accepts empty HMAC keys, bypassing PyJWT's empty-key validation
- Affected
- >=2.13.0 <2.14.0
- Fixed in
- 2.14.0
PyJWT: Uncaught RecursionError in jwt.decode() on deeply nested token header
- Affected
- >=2.13.0 <2.14.0
- Fixed in
- 2.14.0
PyJWT: Non-canonical signature segments enable raw-token revocation bypass
- Affected
- <2.14.0
- Fixed in
- 2.14.0
PyJWT: Asymmetric-PEM detection bypass: whitespace/line-ending-mutated public keys skip the HS/asymmetric confusion guard
- Affected
- <2.14.0
- Fixed in
- 2.14.0
PyJWT accepts public JWK containers as HMAC secrets
- Affected
- >=2.13.0 <2.14.0
- Fixed in
- 2.14.0
PyJWT: PyJWKClient follows redirects when fetching JWKS
- Affected
- <2.14.0
- Fixed in
- 2.14.0
PyJWT: Public keys in DER form are accepted as HMAC secrets, bypassing the CVE-2022-29217 guard
- Affected
- >=2.4.0 <2.14.0
- Fixed in
- 2.14.0
PyJWT BOM Bypass
- Affected
- >=2.13.0 <2.14.0
- Fixed in
- 2.14.0
PyJWT: PyJWKClient still amplifies unauthenticated JWKS fetches on unknown kid values (incomplete fix of CVE-2026-48524)
- Affected
- <2.14.0
- Fixed in
- 2.14.0
PyJWT: Malformed RSA JWK aborts parsing of an entire JWK Set
- Affected
- >=2.9.0 <2.14.0
- Fixed in
- 2.14.0
Which of your client projects are still on pyjwt 2.13?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact pyjwt version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other pyjwt versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.