PYSEC-2026-176

See a problem?
Import Source
https://github.com/pypa/advisory-database/blob/main/vulns/pyjwt/PYSEC-2026-176.yaml
JSON Data
https://api.osv.dev/v1/vulns/PYSEC-2026-176
Aliases
  • CVE-2026-48523
  • GHSA-jq35-7prp-9v3f
Published
2026-05-28T16:16:29.280Z
Modified
2026-06-02T12:15:10.358230706Z
Severity
  • 5.4 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N CVSS Calculator
Summary
[none]
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.decodecomplete() 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.getsigningkeyfrom_jwt(...) flow. This vulnerability is fixed in 2.13.0.

References

Affected packages

PyPI / pyjwt

Package

Affected ranges

Type
ECOSYSTEM
Events
Introduced
2.9.0
Fixed
2.12.1

Affected versions

2.*
2.9.0
2.10.0
2.10.1
2.11.0
2.12.0

Database specific

source
"https://github.com/pypa/advisory-database/blob/main/vulns/pyjwt/PYSEC-2026-176.yaml"