Secuno
ENNL
Book demo

CVE-2026-32597

Pyjwt broken access control

7.5 HIGHPublic exploitEPSS 0.28%
  1. Published13 Mar 2026

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 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityNone
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected products

Pyjwt< 2.12.0

Remediation

Fixed in
Pyjwt≥ 2.12.0

References

and 25 more references

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-1089719.6
A flaw has been found in D-Link DCS-930L B1.08B4. This impacts the function mpfd_decode…
CVE-2026-163018.5
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before…
CVE-2026-1095598.7
EdgeEver Desktop 1.6.26 through 1.112.0 contains a navigation allowlist bypass that…
CVE-2026-773669.9
obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian…
CVE-2026-1039038.8
An incorrect authorization vulnerability in the WinBox authentication flow of MikroTik…
CVE-2026-1087468.8
Vearch 3.5.2 through 3.5.9 contains an incorrect authorization vulnerability in…

Frequently asked

Is CVE-2026-32597 being actively exploited?

CVE-2026-32597 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.28%.

How severe is CVE-2026-32597?

CVE-2026-32597 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.28% probability of exploitation.

Which products are affected by CVE-2026-32597?

Affected products include Pyjwt.

How do I fix CVE-2026-32597?

Upgrade affected software to a fixed version, for example Pyjwt 2.12.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-32597 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.