Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…
EPSS 0.0%top 97%

CVE-2026-32597: CWE-345: Insufficient Verification of Data Authenticity in jpadilla pyjwt

0
High
VulnerabilityCVE-2026-32597cvecve-2026-32597cwe-345cwe-863
Published: Thu Mar 12 2026 (03/12/2026, 21:41:50 UTC)
Source: CVE Database V5
Vendor/Project: jpadilla
Product: pyjwt

Description

PyJWT is a JSON Web Token implementation in Python. Prior to 2.12.0, PyJWT does not validate the crit (Critical) Header Parameter defined in RFC 7515 §4.1.11. When a JWS token contains a crit array listing extensions that PyJWT does not understand, the library accepts the token instead of rejecting it. This violates the MUST requirement in the RFC. This vulnerability is fixed in 2.12.0.

CVSS v3.1

Score 7.5high

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected software

Affected versions
<2.12.0

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 05/06/2026, 01:42:55 UTC

Technical Analysis

PyJWT, a Python library for JSON Web Tokens, before version 2.12.0, fails to enforce the mandatory validation of the 'crit' header parameter as specified in RFC 7515 §4.1.11. When a JWS token includes a 'crit' array listing extensions that PyJWT does not understand, the library incorrectly accepts the token rather than rejecting it. This behavior constitutes insufficient verification of data authenticity (CWE-345) and improper handling of critical extensions (CWE-863). The vulnerability has a CVSS 3.1 score of 7.5, indicating high severity, and was addressed by the vendor in version 2.12.0.

Potential Impact

This vulnerability allows attackers to craft JSON Web Tokens with unrecognized critical extensions that PyJWT will accept without proper validation. This can lead to acceptance of tokens that should be rejected, potentially enabling unauthorized actions or bypassing security controls relying on token validation. There is no indication of known exploits in the wild at this time.

Mitigation Recommendations

Upgrade PyJWT to version 2.12.0 or later, where the validation of the 'crit' header parameter is correctly implemented in accordance with RFC 7515 §4.1.11. No other mitigation is required as the vendor has provided an official fix.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-12T14:54:24.269Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69b3375b2f860ef943024596

Added to database: 3/12/2026, 9:59:55 PM

Last enriched: 5/6/2026, 1:42:55 AM

Last updated: 6/11/2026, 9:23:43 AM

Views: 339

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses