pyjwt vulnerabilities
JSON Web Token implementation in Python
- Registry
- PyPI
- Latest
- 2.15.1
- License
- MIT
25 known advisories
The latest version, 2.15.1, is not affected by any of them. Projects on older versions may be.
pip install 'pyjwt>=2.15.1'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
Security advisories for pyjwt
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
PyJWT: Unauthenticated DoS via unbounded Base64URL decoding of unused payload segment in b64=false detached JWS
- Affected
- >=2.8.0 <2.13.0
- Fixed in
- 2.13.0
PyJWKClient: missing scheme allowlist enables CVE-2024-21643-class SSRF + token forgery via file://, ftp://, data: schemes
- Affected
- >=2.0.0 <2.13.0
- Fixed in
- 2.13.0
PyJWT: Public-key JWK accepted as HMAC secret enables forged HS256 tokens when mixed families are allowed
- Affected
- <2.13.0
- Fixed in
- 2.13.0
PyJWT: Algorithm allow-list bypass when decoding with `PyJWK` / `PyJWKClient` keys
- Affected
- >=2.9.0 <2.13.0
- Fixed in
- 2.13.0
PyJWKClient unbounded JWKS endpoint requests via attacker-controlled kid values (DoS)
- Affected
- >=2.0.0 <2.13.0
- Fixed in
- 2.13.0
PyJWT accepts unknown `crit` header extensions
- Affected
- <2.12.0
- Fixed in
- 2.12.0
No summary published
- Affected
- <=2.10.1
- Fixed in
- No fix released
PyJWT Issuer field partial matches allowed
- Affected
- >=2.10.0 <2.10.1
- Fixed in
- 2.10.1
Key confusion through non-blocklisted public key formats
- Affected
- >=1.5.0 <2.4.0
- Fixed in
- 2.4.0
PyJWT vulnerable to key confusion attacks
- Affected
- <1.5.1
- Fixed in
- 1.5.1
Is your pyjwt version vulnerable?
- pyjwt 2.15No known advisories in 2.15.1
- pyjwt 2.142 advisories in 2.14.0
- pyjwt 2.1315 advisories in 2.13.0
- pyjwt 2.1216 advisories in 2.12.1
- pyjwt 2.1117 advisories in 2.11.0
- pyjwt 2.1017 advisories in 2.10.1
- pyjwt 1.710 advisories in 1.7.1
- pyjwt 1.610 advisories in 1.6.4
- pyjwt 1.510 advisories in 1.5.3
- pyjwt 1.410 advisories in 1.4.2
- pyjwt 1.310 advisories in 1.3.0
- pyjwt 1.110 advisories in 1.1.0
- pyjwt 0.410 advisories in 0.4.3
- pyjwt 0.310 advisories in 0.3.2
- pyjwt 0.210 advisories in 0.2.3
- pyjwt 0.110 advisories in 0.1.9
Which of your client projects still run an old pyjwt?
NPMscan reads the requirements.txt, poetry.lock, uv.lock and Pipfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other PyPI packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the PyPI registry.