Skip to main content
VulnerabilityPublished Updated

CVE-2026-32597: jpadilla pyjwt · Insufficient Verification of Data Authenticity

Affects jpadilla pyjwtSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 2.12.0 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.12.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade jpadilla pyjwt to 2.12.0.

Affected software

ProductAffectedFixed in
jpadillapyjwtAffected
  • <2.12.0
Fixed in
  • 2.12.0
PyPIpyjwtpkg:pypi/pyjwtOther threatsAffected
  • <2.12.0
Fixed in
  • 2.12.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in PyJWT version 2.12.0. Users should upgrade to version 2.12.0 or later to ensure proper validation of the 'crit' header parameter as per RFC 7515 §4.1.11. The Red Hat advisory notes that mitigation options other than upgrading do not meet their criteria for ease of use and applicability. Therefore, upgrading is the recommended remediation.

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.

References

Community reviews

Loading reviews…