CVE-2026-48523

EUVD-2026-32918
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.
ProviderTypeBase ScoreAtk. VectorAtk. ComplexityPriv. RequiredVector
NISTPrimary
5.4 MEDIUM
NETWORK
LOW
LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Base Score
CVSS 3.x
EPSS Score
Percentile: 2%
Affected Products (NVD)
VendorProductVersion
pyjwt_projectpyjwt
2.9.0 ≤
𝑥
< 2.12.1
𝑥
= Vulnerable software versions
openSUSE logo
openSUSE / SLES Releases
openSUSE Product
Release
python3-PyJWT
suse enterprise sap 15 SP4
2.4.0-150200.3.14.1
fixed
suse enterprise sap 15 SP5
2.4.0-150200.3.14.1
fixed
suse enterprise sap 15 SP6
2.4.0-150200.3.14.1
fixed
suse enterprise server 15 SP4
2.4.0-150200.3.14.1
fixed
suse enterprise server 15 SP5
2.4.0-150200.3.14.1
fixed
suse enterprise server 15 SP6
2.4.0-150200.3.14.1
fixed
python311-PyJWT
suse enterprise sap 15 SP4
2.8.0-150400.8.13.1
fixed
suse enterprise sap 15 SP5
2.8.0-150400.8.13.1
fixed
suse enterprise sap 15 SP6
2.8.0-150400.8.13.1
fixed
suse enterprise server 15 SP4
2.8.0-150400.8.13.1
fixed
suse enterprise server 15 SP5
2.8.0-150400.8.13.1
fixed
suse enterprise server 15 SP6
2.8.0-150400.8.13.1
fixed