Vulnerabilities for PyJWT

First version without a known vulnerability: 2.13.0

Details

• GHSA-w7vc-732c-9m392026-06-15

  PyJWT: Unauthenticated DoS via unbounded Base64URL decoding of unused payload segment in b64=false detached JWS

  Fixed in: 2.13.0

• GHSA-993g-76c3-p5m42026-06-15

  PyJWKClient: missing scheme allowlist enables CVE-2024-21643-class SSRF + token forgery via file://, ftp://, data: schemes

  Fixed in: 2.13.0

• GHSA-xgmm-8j9v-c9wx2026-06-15

  PyJWT: Public-key JWK accepted as HMAC secret enables forged HS256 tokens when mixed families are allowed

  Fixed in: 2.13.0

• GHSA-jq35-7prp-9v3f2026-06-15

  PyJWT: Algorithm allow-list bypass when decoding with `PyJWK` / `PyJWKClient` keys

  Fixed in: 2.13.0, 2.12.1

• GHSA-fhv5-28vv-h8m82026-06-15

  PyJWKClient unbounded JWKS endpoint requests via attacker-controlled kid values (DoS)

  Fixed in: 2.13.0

• GHSA-752w-5fwx-jx9f2026-03-13

  PyJWT accepts unknown `crit` header extensions

  Fixed in: 2.12.0

• PYSEC-2025-1832025-07-31

  pyjwt v2.10.1 was discovered to contain weak encryption. NOTE: this is disputed by the Supplier because the key length is chosen by the application that uses the library (admittedly, library users may benefit from a minimum value and a mechanism for opting in to strict enforcement).

• GHSA-75c5-xw7c-p5pm2024-12-02

  PyJWT Issuer field partial matches allowed

  Fixed in: 2.10.1

• GHSA-ffqj-6fqr-9h242022-05-24

  Key confusion through non-blocklisted public key formats

  Fixed in: 2.4.0, 9c528670c455b8d948aff95ed50e22940d1ad3fc

• GHSA-r9jw-mwhq-wp622022-05-13

  PyJWT vulnerable to key confusion attacks

  Fixed in: 1.5.1