● PyPI package
pyjwt
Pyjwt has 25 security advisories. The newest release any of them names as the fix is 2.15.0.
As of , pyjwt has 25 security advisories. The newest release any of them names as the fix is 2.15.0.
Your version, and the version to upgrade to
| If you run | Upgrade to | Advisories |
|---|---|---|
| Before 2.15.0 | 2.15.0 | 25 advisories |
Security advisories, newest first
| Advisory | What it is | Affects | Fixed in | Published |
|---|---|---|---|---|
| GHSA-pxh4-856f-4h89 | PyJWT: HS256/384/512 verify accepts empty HMAC key via oct JWK (PyJWK/PyJWKClient) enabling token forgeryHigh severity | Before 2.14.0 | 2.14.0 | |
| CVE-2026-103001GHSA-gvp8-978c-rx2q, PYSEC-2026-4146 | PyJWT.decode() reintroduces options-dict mutation, enabling silent claim-verification bypass on dict reuseModerate severity | From 2.11.0 up to and including 2.13.0 | No fixed version listed | |
| CVE-2026-101918GHSA-42vr-xj54-vc7v, PYSEC-2026-4141 | PyJWT: Unauthenticated RecursionError DoS in pre-verification payload parse (PyJWKClient.get_signing_key_from_jwt / verify_signature=False)Moderate severity | From 2.0.0a1 before 2.15.0 | 2.15.0 | |
| CVE-2026-102270GHSA-jwrc-g2q2-pq5p, PYSEC-2026-4148 | PyJWT: ReDoS vulnerability when calling the `is_pem_format` function.Moderate severity | Before 2.14.0 | 2.14.0 | |
| CVE-2026-102266GHSA-9j54-fg26-wv3r, PYSEC-2026-4143 | PyJWT: PyJWK accepts empty HMAC keys, bypassing PyJWT's empty-key validationHigh severity | From 2.13.0 before 2.14.0 | 2.14.0 | |
| CVE-2026-102265GHSA-8wjv-2p76-3863, PYSEC-2026-4142 | PyJWT: Uncaught RecursionError in jwt.decode() on deeply nested token headerModerate severity | From 2.13.0 before 2.14.0 | 2.14.0 | |
| CVE-2026-102269GHSA-hxm8-2xgr-2p9m, PYSEC-2026-4147 | PyJWT: Non-canonical signature segments enable raw-token revocation bypassModerate severity | Before 2.14.0 | 2.14.0 | |
| CVE-2026-102268GHSA-ffc3-869f-jxw9, PYSEC-2026-4145 | PyJWT: Asymmetric-PEM detection bypass: whitespace/line-ending-mutated public keys skip the HS/asymmetric confusion guardCritical severity | Before 2.14.0 | 2.14.0 | |
| CVE-2026-102273GHSA-w2cx-738m-mc7w, PYSEC-2026-4151 | PyJWT accepts public JWK containers as HMAC secretsHigh severity | From 2.13.0 before 2.14.0 | 2.14.0 | |
| CVE-2026-102267GHSA-9v7f-9g4p-ffgj, PYSEC-2026-4144 | PyJWT: PyJWKClient follows redirects when fetching JWKSHigh severity | Before 2.14.0 | 2.14.0 | |
| CVE-2026-102271GHSA-p4g4-x82p-q773, PYSEC-2026-4149 | PyJWT: Public keys in DER form are accepted as HMAC secrets, bypassing the CVE-2022-29217 guardHigh severity | From 2.4.0 before 2.14.0 | 2.14.0 | |
| CVE-2026-102272GHSA-r6x4-923q-g947, PYSEC-2026-4150 | PyJWT BOM BypassHigh severity | From 2.13.0 before 2.14.0 | 2.14.0 | |
| CVE-2026-101917GHSA-2gx3-rcp4-g85q, PYSEC-2026-4140 | PyJWT: PyJWKClient still amplifies unauthenticated JWKS fetches on unknown kid values (incomplete fix of CVE-2026-48524)Moderate severity | Before 2.14.0 | 2.14.0 | |
| CVE-2026-102274GHSA-w6j9-cwv2-h6wq, PYSEC-2026-4152 | PyJWT: Malformed RSA JWK aborts parsing of an entire JWK SetModerate severity | From 2.9.0 before 2.14.0 | 2.14.0 | |
| CVE-2026-102275GHSA-x33g-cr3x-6449, PYSEC-2026-4183 | PyJWT accepts inconsistent OKP x/d JWKs, causing public/private key identity confusionModerate severity | From 2.1.0 before 2.15.0 | 2.15.0 | |
| CVE-2026-48526GHSA-xgmm-8j9v-c9wx, PYSEC-2026-179 | PyJWT: Public-key JWK accepted as HMAC secret enables forged HS256 tokens when mixed families are allowedHigh severity | Before 2.13.0 | 2.13.0 | |
| CVE-2026-48525GHSA-w7vc-732c-9m39, PYSEC-2026-178 | PyJWT: Unauthenticated DoS via unbounded Base64URL decoding of unused payload segment in b64=false detached JWSModerate severity | From 2.8.0 before 2.13.0 | 2.13.0 | |
| CVE-2026-48524GHSA-fhv5-28vv-h8m8, PYSEC-2026-177 | PyJWKClient unbounded JWKS endpoint requests via attacker-controlled kid values (DoS)Low severity | Before 2.13.0 | 2.13.0 | |
| CVE-2026-48523GHSA-jq35-7prp-9v3f, PYSEC-2026-176 | PyJWT: Algorithm allow-list bypass when decoding with `PyJWK` / `PyJWKClient` keysModerate severity | From 2.9.0 before 2.13.0 | 2.13.0 | |
| CVE-2026-48522GHSA-993g-76c3-p5m4, PYSEC-2026-175 | PyJWKClient: missing scheme allowlist enables CVE-2024-21643-class SSRF + token forgery via file://, ftp://, data: schemesModerate severity | Before 2.13.0 | 2.13.0 | |
| CVE-2026-32597GHSA-752w-5fwx-jx9f, PYSEC-2026-120 | PyJWT accepts unknown `crit` header extensionsHigh severity | Before 2.12.0 | 2.12.0 | |
| CVE-2025-45768PYSEC-2025-183 | pyjwt v2.10.1 was discovered to contain weak encryption. | Up to and including 2.10.1 | No fixed version listed | |
| CVE-2024-53861GHSA-75c5-xw7c-p5pm, PYSEC-2026-1814 | PyJWT Issuer field partial matches allowedLow severity | From 2.10.0 before 2.10.1 | 2.10.1 | |
| CVE-2022-29217GHSA-ffqj-6fqr-9h24, PYSEC-2022-202 | Key confusion through non-blocklisted public key formatsHigh severity | From 1.5.0 before 2.4.0 | 2.4.0 | |
| CVE-2017-11424GHSA-r9jw-mwhq-wp62, PYSEC-2017-24 | PyJWT vulnerable to key confusion attacksHigh severity | Before 1.5.1 | 1.5.1 |
Other PyPI packages
- glances26 advisories
- octoprint25 advisories
- cryptography24 advisories
- lollms24 advisories