CVE-2026-62995: CWE-345: Insufficient Verification of Data Authenticity in authlib joserfc
The joserfc Python library versions 1.7.1 and earlier accept JSON Web Tokens (JWTs) with trailing padding characters (==), which violates JOSE specifications and causes token malleability. This malleability can potentially allow bypassing token revocation or anti-replay protections that rely on deny lists of tokens or token hashes. The issue has been fixed in version 1.7.2.
AI Analysis
Technical Summary
joserfc, a Python library implementing JOSE standards, in versions up to 1.7.1 accepts JWTs containing trailing padding ('=='), which is non-compliant with JOSE specifications. This acceptance leads to malleability of JWTs, meaning tokens can be altered without invalidating their signature under certain signature schemes. Such malleability may undermine security mechanisms like token revocation or anti-replay protections that depend on the assumption that tokens are immutable. The vulnerability does not affect ECDSA JWS tokens uniquely, as ECDSA signatures are inherently malleable. The issue was addressed and fixed in version 1.7.2.
Potential Impact
The vulnerability allows JWT malleability in affected versions, which could enable attackers to bypass token revocation or anti-replay protections if these rely on deny lists of tokens or token hashes. The impact is limited and context-dependent, as it depends on how the application uses joserfc and manages token validation. The CVSS score is low (2.3), reflecting limited impact and exploitability.
Mitigation Recommendations
Upgrade joserfc to version 1.7.2 or later, where this issue has been fixed. There is no indication of official vendor advisory or temporary fixes, but the fix is available in the newer version. No additional mitigation is specified or required beyond applying the update.
CVE-2026-62995: CWE-345: Insufficient Verification of Data Authenticity in authlib joserfc
Description
The joserfc Python library versions 1.7.1 and earlier accept JSON Web Tokens (JWTs) with trailing padding characters (==), which violates JOSE specifications and causes token malleability. This malleability can potentially allow bypassing token revocation or anti-replay protections that rely on deny lists of tokens or token hashes. The issue has been fixed in version 1.7.2.
CVSS v4.0
Score 2.3low
Affected software
authlib
joserfc
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
joserfc, a Python library implementing JOSE standards, in versions up to 1.7.1 accepts JWTs containing trailing padding ('=='), which is non-compliant with JOSE specifications. This acceptance leads to malleability of JWTs, meaning tokens can be altered without invalidating their signature under certain signature schemes. Such malleability may undermine security mechanisms like token revocation or anti-replay protections that depend on the assumption that tokens are immutable. The vulnerability does not affect ECDSA JWS tokens uniquely, as ECDSA signatures are inherently malleable. The issue was addressed and fixed in version 1.7.2.
Potential Impact
The vulnerability allows JWT malleability in affected versions, which could enable attackers to bypass token revocation or anti-replay protections if these rely on deny lists of tokens or token hashes. The impact is limited and context-dependent, as it depends on how the application uses joserfc and manages token validation. The CVSS score is low (2.3), reflecting limited impact and exploitability.
Mitigation Recommendations
Upgrade joserfc to version 1.7.2 or later, where this issue has been fixed. There is no indication of official vendor advisory or temporary fixes, but the fix is available in the newer version. No additional mitigation is specified or required beyond applying the update.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-14T23:10:57.032Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a6a48789c2644c7f8e5158f
Added to database: 07/29/2026, 18:37:44 UTC
Last enriched: 08/06/2026, 17:53:35 UTC
Last updated: 09/10/2026, 19:59:58 UTC
Views: 76
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.
External Links
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.