Incorrect Behavior Order: Validate Before Canonicalize Affecting python313-PyJWT package, versions <2.12.1-160000.3.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.22% (13th 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-SLES1600-PYTHON313PYJWT-21351106
  • published21 Oct 2026
  • disclosed9 Oct 2026

Introduced: 9 Oct 2026

NewCVE-2026-102269  (opens in a new tab)
CWE-180  (opens in a new tab)

How to fix?

Upgrade SLES:16.0.0 python313-PyJWT to version 2.12.1-160000.3.1 or higher.

NVD Description

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

PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT signature segment is affected because signature segment decoding accepts characters outside the canonical Base64URL representation. This occurs when non-Base64URL characters are appended to a valid compact JWS signature segment. As a result, base64url_decode produces the same signature bytes for different serialized segments. Consequently, raw-token revocation checks can fail to recognize an equivalent modified token. This issue is fixed in version 2.14.0.

CVSS Base Scores

version 3.1