CVE-2026-32597

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
EPSS PROB
0.3%
EPSS %ILE
18th
KEV
Not listed

Published

March 13, 2026

Last Modified

September 10, 2026

Advisory Details (2)

Auto-updated May 6, 2026
🔬 Proof of concept available. Patch available. Sources: github.
githubMentions a patch (unverified)🟡 PoC Available

PyJWT accepts unknown `crit` header extensions · Advisory · jpadilla/pyjwt · GitHub

https://github.com/jpadilla/pyjwt/security/advisories/GHSA-752w-5fwx-jx9f
genericMentions a patch (unverified)

[SECURITY] [DLA 4564-1] pyjwt security update

https://lists.debian.org/debian-lts-announce/2026/05/msg00008.html

Vendor Advisories for CVE-2026-32597(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(29)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17836154322026-07-21redhat
redhatrhoai/odh-trustyai-garak-lls-provider-dsp-rhel9:17824723742026-07-09redhat
redhatsatellite/iop-host-inventory-rhel9:17804142372026-06-16redhat
redhatrhoai/odh-vllm-gaudi-rhel9:17800690692026-06-10redhat
redhatfence-agents-0:4.10.0-43.el9_2.212026-06-01redhat
redhatfence-agents-0:4.10.0-62.el9_4.242026-05-28redhat
redhatfence-agents-0:4.10.0-86.el9_6.162026-05-27redhat
redhatrhoai/odh-vllm-gaudi-rhel9:17786001872026-05-20redhat
redhatfence-agents-0:4.10.0-110.el9_8.22026-05-19redhat
redhatquay/quay-rhel9:17792040862026-05-19redhat
redhatfence-agents-0:4.16.0-21.el10_2.12026-05-19redhat
redhatfence-agents-0:4.16.0-5.el10_0.92026-05-13redhat
redhatfence-agents-0:4.16.0-13.el10_1.42026-05-06redhat
redhatfence-agents-0:4.10.0-98.el9_7.122026-05-05redhat
redhatansible-automation-platform-25/lightspeed-rhel8:17774038722026-05-04redhat
redhatpython3.12-pyjwt-0:2.12.1-1.el9ap2026-05-04redhat
redhatansible-automation-platform-26/mcp-tools-rhel9:17773116012026-05-04redhat
redhatfence-agents-0:4.2.1-129.el8_10.252026-04-30redhat
redhatrhelai3/disk-image-cuda-rhel9:17769388712026-04-23redhat
redhatrhoai/odh-kserve-storage-initializer-rhel9:17763431112026-04-23redhat
redhatrhelai3/bootc-rocm-rhel9:17767735052026-04-23redhat
redhatrhaiis/vllm-rocm-rhel9:17756802622026-04-17redhat
redhatrhaiis/model-opt-cuda-rhel9:17757498572026-04-17redhat
redhatrhaiis/vllm-cuda-rhel9:17756801922026-04-17redhat
redhatrhtas/model-transparency-rhel9:17758154072026-04-16redhat
redhatquay/quay-rhel8:17751691552026-04-07redhat
redhatquay/quay-rhel8:17751692182026-04-07redhat
redhatquay/quay-rhel8:17752530922026-04-06redhat
redhatquay/quay-rhel8:17751692192026-04-03redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
pyjwt1.7.1-2
  • every version up to 1.7.1-2+deb11u1: fixed in 1.7.1-2+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
pyjwt2.6.0-1
  • every version up to 2.6.0-1+deb12u1: fixed in 2.6.0-1+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pyjwt2.10.1-2
  • every version up to 2.10.1-2+deb13u1: fixed in 2.10.1-2+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pyjwt2.10.1-2, 2.10.1-3, 2.10.1-4, 2.11.0-2
  • every version up to 2.12.1-1: fixed in 2.12.1-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pyjwt0.1.1 ... 2.9.0 (52 versions)
  • every version up to 2.12.0: fixed in 2.12.0
—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(6)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 235 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:47 UTCEPSS rescore
  4. 2026-10-06 15:17 UTCEPSS rescore
  5. 2026-10-05 17:42 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:49 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-29 19:32 UTCOSV refresh
  11. 2026-09-28 13:51 UTCEPSS rescore
  12. 2026-09-27 13:48 UTCEPSS rescore
  13. 2026-09-26 15:58 UTCEPSS rescore
  14. 2026-09-26 00:26 UTCEPSS rescore
  15. 2026-09-20 20:15 UTCEPSS rescore
  16. 2026-09-20 20:15 UTCEPSS rescore
  17. 2026-09-18 19:28 UTCEPSS rescore
  18. 2026-09-18 19:27 UTCEPSS rescore
  19. 2026-09-17 19:30 UTCEPSS rescore
  20. 2026-09-16 14:08 UTCEPSS rescore
  21. 2026-09-16 05:15 UTCEPSS rescore
  22. 2026-09-13 16:47 UTCEPSS rescore
  23. 2026-09-12 15:01 UTCEPSS rescore
  24. 2026-09-11 14:52 UTCEPSS rescore
  25. 2026-09-10 13:22 UTCEG score recompute
Show 75 more
  1. 2026-09-10 13:22 UTCVendor advisory
  2. 2026-09-10 12:28 UTCEG score recompute
  3. 2026-09-10 12:28 UTCVendor advisory
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-08 22:00 UTCEPSS rescore
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-07 14:03 UTCEG score recompute
  8. 2026-09-07 14:03 UTCVendor advisory
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-04 05:06 UTCEPSS rescore
  12. 2026-09-02 14:11 UTCEPSS rescore
  13. 2026-09-01 13:53 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-09-01 04:39 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-24 14:17 UTCEPSS rescore
  23. 2026-08-24 12:27 UTCEG score recompute
  24. 2026-08-24 12:27 UTCVendor advisory
  25. 2026-08-23 00:19 UTCEPSS rescore
  26. 2026-08-21 23:49 UTCEPSS rescore
  27. 2026-08-20 22:55 UTCEPSS rescore
  28. 2026-08-20 22:55 UTCEPSS rescore
  29. 2026-08-19 17:03 UTCEPSS rescore
  30. 2026-08-18 13:48 UTCEPSS rescore
  31. 2026-08-17 13:47 UTCEPSS rescore
  32. 2026-08-17 12:21 UTCEG score recompute
  33. 2026-08-17 12:21 UTCVendor advisory
  34. 2026-08-17 12:13 UTCEG score recompute
  35. 2026-08-17 12:13 UTCVendor advisory
  36. 2026-08-16 14:56 UTCEPSS rescore
  37. 2026-08-16 11:34 UTCEG score recompute
  38. 2026-08-16 11:34 UTCVendor advisory
  39. 2026-08-16 02:14 UTCEPSS rescore
  40. 2026-08-15 01:30 UTCEPSS rescore
  41. 2026-08-14 20:03 UTCVendor advisory
  42. 2026-08-14 07:36 UTCEG score recompute
  43. 2026-08-14 07:36 UTCVendor advisory
  44. 2026-08-13 22:00 UTCEPSS rescore
  45. 2026-08-12 23:56 UTCEG score recompute
  46. 2026-08-12 23:56 UTCVendor advisory
  47. 2026-08-12 13:50 UTCEPSS rescore
  48. 2026-08-12 12:39 UTCEG score recompute
  49. 2026-08-12 12:39 UTCVendor advisory
  50. 2026-08-12 12:14 UTCVendor advisory
  51. 2026-08-11 21:39 UTCEG score recompute
  52. 2026-08-11 21:39 UTCVendor advisory
  53. 2026-08-11 04:47 UTCEG score recompute
  54. 2026-08-11 04:47 UTCVendor advisory
  55. 2026-08-11 00:00 UTCEPSS rescore
  56. 2026-08-10 05:53 UTCVendor advisory
  57. 2026-08-09 18:31 UTCEG score recompute
  58. 2026-08-09 18:31 UTCVendor advisory
  59. 2026-08-09 13:46 UTCEPSS rescore
  60. 2026-08-09 07:13 UTCEG score recompute
  61. 2026-08-09 07:13 UTCVendor advisory
  62. 2026-08-08 16:37 UTCEPSS rescore
  63. 2026-08-08 05:12 UTCVendor advisory
  64. 2026-08-07 17:54 UTCEG score recompute
  65. 2026-08-07 17:54 UTCVendor advisory
  66. 2026-08-06 19:46 UTCEG score recompute
  67. 2026-08-06 19:46 UTCVendor advisory
  68. 2026-08-06 13:46 UTCEPSS rescore
  69. 2026-08-06 01:50 UTCEG score recompute
  70. 2026-08-06 01:50 UTCVendor advisory
  71. 2026-08-05 19:17 UTCEPSS rescore
  72. 2026-08-04 15:10 UTCEPSS rescore
  73. 2026-08-04 10:38 UTCEPSS rescore
  74. 2026-08-04 01:06 UTCVendor advisory
  75. 2026-08-03 12:50 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-32597?
CVE-2026-32597 is a high vulnerability published on March 13, 2026. 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…
When was CVE-2026-32597 disclosed?
CVE-2026-32597 was first published on March 13, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32597 actively exploited?
CVE-2026-32597 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-32597?
CVE-2026-32597 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-32597?
A fix for CVE-2026-32597 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-32597 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32597

Explore →

Is Your Infrastructure Affected by CVE-2026-32597?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs