CVE-2026-102269: CWE-180: Incorrect Behavior Order: Validate Before Canonicalize in jpadilla pyjwt
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.
AI Analysis
Technical Summary
PyJWT, a Python implementation of JSON Web Token standards, has a vulnerability (CWE-180) in versions before 2.14.0 where the signature segment decoding accepts characters outside the canonical Base64URL set. When non-Base64URL characters are appended to a valid compact JWS signature segment, base64url_decode produces the same signature bytes for different serialized segments. This can cause raw-token revocation checks to fail to recognize modified tokens as equivalent, potentially allowing revoked tokens to be accepted. The vulnerability is addressed in PyJWT version 2.14.0.
Potential Impact
The vulnerability allows different serialized tokens with appended non-Base64URL characters to decode to the same signature bytes, which can cause token revocation mechanisms that rely on raw token comparison to fail. This may lead to acceptance of revoked tokens, impacting the integrity of token validation. The CVSS score is 4.8 (medium severity), indicating limited impact with network attack vector, high attack complexity, no privileges required, no user interaction, and low confidentiality and integrity impact.
Mitigation Recommendations
Upgrade PyJWT to version 2.14.0 or later where this issue is fixed. No other mitigations are indicated by the vendor advisory. Patch status is confirmed fixed in 2.14.0.
CVE-2026-102269: CWE-180: Incorrect Behavior Order: Validate Before Canonicalize in jpadilla pyjwt
Description
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 v3.1
Score 4.8medium
Affected software
jpadilla
pyjwt
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
PyJWT, a Python implementation of JSON Web Token standards, has a vulnerability (CWE-180) in versions before 2.14.0 where the signature segment decoding accepts characters outside the canonical Base64URL set. When non-Base64URL characters are appended to a valid compact JWS signature segment, base64url_decode produces the same signature bytes for different serialized segments. This can cause raw-token revocation checks to fail to recognize modified tokens as equivalent, potentially allowing revoked tokens to be accepted. The vulnerability is addressed in PyJWT version 2.14.0.
Potential Impact
The vulnerability allows different serialized tokens with appended non-Base64URL characters to decode to the same signature bytes, which can cause token revocation mechanisms that rely on raw token comparison to fail. This may lead to acceptance of revoked tokens, impacting the integrity of token validation. The CVSS score is 4.8 (medium severity), indicating limited impact with network attack vector, high attack complexity, no privileges required, no user interaction, and low confidentiality and integrity impact.
Mitigation Recommendations
Upgrade PyJWT to version 2.14.0 or later where this issue is fixed. No other mitigations are indicated by the vendor advisory. Patch status is confirmed fixed in 2.14.0.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-09-28T20:11:16.658Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6abad294f7a7c541062fe5bd
Added to database: 09/28/2026, 20:48:20 UTC
Last enriched: 09/28/2026, 21:03:03 UTC
Last updated: 09/29/2026, 02:48:28 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.