Is pyjwt safe? Known vulnerabilities by version

pyjwt is a Python package on PyPI. We track 2 of its versions: 1 of them has known vulnerabilities.

Latest version without known advisories: 2.15.1

The newest stable version we track with no known advisory, as of 22 November 2026. A newer release may exist on PyPI.

Vulnerabilities by version

VersionKnown vulnerabilitiesHighest severityLicence
2.15.1 0 None MIT
2.8.0 15 Critical MIT

Every advisory for pyjwt

  • Critical CVSS 9.1

    CVE-2026-102268: PyJWT: Asymmetric-PEM detection bypass: whitespace/line-ending-mutated public keys skip the HS/asymmetric confusion guard

    Affects 2.8.0 (of the versions we track).

  • High CVSS 7.5

    CVE-2026-32597: PyJWT accepts unknown `crit` header extensions

    Affects 2.8.0 (of the versions we track).

  • High CVSS 7.4

    CVE-2026-102267: PyJWT: PyJWKClient follows redirects when fetching JWKS

    Affects 2.8.0 (of the versions we track).

  • High CVSS 7.4

    CVE-2026-102271: PyJWT: Public keys in DER form are accepted as HMAC secrets, bypassing the CVE-2022-29217 guard

    Affects 2.8.0 (of the versions we track).

  • High CVSS 7.4

    GHSA-pxh4-856f-4h89: PyJWT: HS256/384/512 verify accepts empty HMAC key via oct JWK (PyJWK/PyJWKClient) enabling token forgery

    Affects 2.8.0 (of the versions we track).

  • High CVSS 7.4

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

    Affects 2.8.0 (of the versions we track).

  • High CVSS 7.0

    CVE-2025-45768

    Affects 2.8.0 (of the versions we track).

  • Medium CVSS 5.3

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

    Affects 2.8.0 (of the versions we track).

  • Medium CVSS 5.3

    CVE-2026-101918: PyJWT: Unauthenticated RecursionError DoS in pre-verification payload parse (PyJWKClient.get_signing_key_from_jwt / verify_signature=False)

    Affects 2.8.0 (of the versions we track).

  • Medium CVSS 4.2

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

    Affects 2.8.0 (of the versions we track).

  • Medium CVSS 4.8

    CVE-2026-102269: PyJWT: Non-canonical signature segments enable raw-token revocation bypass

    Affects 2.8.0 (of the versions we track).

  • Medium CVSS 4.4

    CVE-2026-102270: PyJWT: ReDoS vulnerability when calling the `is_pem_format` function.

    Affects 2.8.0 (of the versions we track).

  • Medium CVSS 5.3

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

    Affects 2.8.0 (of the versions we track).

  • Medium CVSS 6.5

    CVE-2026-102275: PyJWT accepts inconsistent OKP x/d JWKs, causing public/private key identity confusion

    Affects 2.8.0 (of the versions we track).

  • Low CVSS 3.7

    CVE-2026-48524: PyJWKClient unbounded JWKS endpoint requests via attacker-controlled kid values (DoS)

    Affects 2.8.0 (of the versions we track).

Licence

Every version we track declares MIT (from deps.dev).

Check your whole project

pyjwt is one package among hundreds in a lockfile. Upload your lockfile, or paste a public GitHub repository, and get every vulnerable package with the version that fixes it. Free, and no account needed.

Get emailed about new advisories for pyjwt (free, no account)

About this data

Vulnerability data: OSV.dev, last checked 22 November 2026. Licences: deps.dev. These pages list the versions AIssue checks every day for the projects it monitors, not every version ever released.