Improper Verification of Cryptographic Signature Affecting python311-PyJWT package, versions <2.8.0-150400.8.13.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.13% (3rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES156-PYTHON311PYJWT-17528159
  • published26 Jun 2026
  • disclosed25 Jun 2026

Introduced: 25 Jun 2026

CVE-2026-48523  (opens in a new tab)
CWE-347  (opens in a new tab)

How to fix?

Upgrade SLES:15.6 python311-PyJWT to version 2.8.0-150400.8.13.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python311-PyJWT package and not the python311-PyJWT package as distributed by SLES. See How to fix? for SLES:15.6 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1