Advisory

PYSEC-2026-176

Also known as: CVE-2026-48523, GHSA-jq35-7prp-9v3f

Summary

The record has no summary.

Details

PyJWT is a JSON Web Token implementation in Python. From 2.9.0 to 2.12.1, there is a verifier-side algorithm allow-list bypass when jwt.decode() or jwt.decode_complete() are called with a PyJWK key. The token header alg is checked against the caller-supplied algorithms allow-list, but signature verification is performed with the algorithm bound to the PyJWK object instead of the header algorithm. An attacker who controls a registered JWK/JWKS private key can sign with a disallowed algorithm, advertise an allowed algorithm in the JWT header, and still be accepted. The issue affects the documented PyJWKClient.get_signing_key_from_jwt(...) flow. This vulnerability is fixed in 2.13.0.

Severity

Medium Basis: CVSS v3 score 5.4, vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Dates

Published
2026-05-28 16:16 UTC
Modified
2026-06-02 12:15 UTC

Affected packages and fixes

pyjwt

PyPI · All systems

Affected

  • introduced 2.9.0, fixed 2.12.1 (ecosystem)

Fixed versions

2.12.1

Fix

  • Fixed version 2.12.1
    pip install --upgrade pyjwt==2.12.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: PyPA Advisory Database · CC BY 4.0

Sources & licences