Incorrect Behavior Order: Validate Before Canonicalize Affecting py3.11-pyjwt package, versions <2.14.0-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.2% (9th 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-MINIMOSLATEST-PY311PYJWT-20344542
  • published1 Oct 2026
  • disclosed28 Sept 2026

Introduced: 28 Sep 2026

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

How to fix?

Upgrade Minimos:latest py3.11-pyjwt to version 2.14.0-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream py3.11-pyjwt package and not the py3.11-pyjwt package as distributed by Minimos. See How to fix? for Minimos:latest 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