CVE-2026-32597Disclosure(pyjwt_project / pyjwt)

LOWCVSS 7.5 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch pyjwt_project pyjwt systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD 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.

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-345CWE-863CWE-347

Priority

LOW

Exploitation

NONE

PoC

YES

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • pyjwt

Threat summary

  • Patch or workaround signal is available
  • 3 mentions across 3 observed days
  • Momentum state: stable

What's happening

  • Patch or workaround mentioned in 2 signals
  • Technical details provided in 2 signals
  • Disclosure: 2 classified signals
  • Peaked 2d ago at 1 mentions (2026-03-12); latest day: 1
  • 3 total mentions across 3 days

Affected systems

Products
pyjwt

Deep dive

Activity timeline3 mentions / 3d
00111Mentions · 2026-03-12: 1Mentions · 2026-03-13: 1Mentions · 2026-08-08: 1Patch / Workaround · 2026-03-12: 1Patch / Workaround · 2026-08-08: 1Technical Details · 2026-03-12: 1Technical Details · 2026-03-13: 103-1203-1308-08
Signal classification2 categories
Disclosure
266.7%
Patch
133.3%
Referenced assets3 URLs
Classification over time
DateTotalLabels
2026-03-121
Disclosure1
2026-03-131
Disclosure1
2026-08-081
Patch1
Full discourse3 posts
  • Windows Forum@windowsforum
    Patch

    🔐 CVE-2026-32597 isn’t a Windows bug—your Python app’s PyJWT dependency is the problem. Update to 2.12.0; Microsoft’s “patch” is basically a strongly worded suggestion. https://windowsforum.com/security-alerts.84/cve-2026-32597-update-pyjwt-to-2-12-0-for-jwt-crit-fix.442036/?utm_source=x&utm_medium=social&utm_campaign=news_node84 #WindowsAdministration #JwtSecurity #Pyjwt #Cve202632597 https://t.co/OEDzFuWlfz

    Post summary

    The post announces a patch recommendation for CVE-2026-32597 by urging an update to PyJWT 2.12.0, clarifying the vulnerability is not a Windows bug, and encouraging users to apply the workaround.

    0000059
    1.3K followersView on X
  • CyberDudeBivash® | Global Cybersecurity Company@cyberbivash
    Disclosure

    🚨 CYBERDUDEBIVASH SENTINEL APEX ALERT 🚨 Threat: CVE-2026-32597 - PyJWT accepts unknown `crit` header extensions (RFC 7515 §4.1.11 MUST violation) Intel Report: https://ift.tt/8AspgLF

    Post summary

    The message announces CVE-2026-32597, revealing a PyJWT handling flaw that violates the RFC, and links to an intel report, with no evidence of exploitation or remediation.

    0000033
    340 followersView on X
  • CVE@CVEnew
    Disclosure

    CVE-2026-32597 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 … https://www.cve.org/CVERecord?id=CVE-2026-32597

    Post summary

    CVE‑2026‑32597 highlights that PyJWT versions before 2.12.0 fail to validate the "crit" header parameter, potentially enabling malicious token exploitation; upgrading to 2.12.0 (or later) mitigates the issue.

    0000079
    56.7K followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Apppyjwt_projectpyjwt---

Explore more