CVE-2026-32597: PyJWT accepts unknown `crit` header extensions (RFC 7515 §4.1.11 MUST violation)
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.27% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: jpadilla pyjwt 2.12.0; azl3 python-jwt 2.8.0-2 on Azure Linux 3.0 2.13.0-1.
Low priority for now. Upgrade to jpadilla pyjwt 2.12.0; azl3 python-jwt 2.8.0-2 on Azure Linux 3.0 2.13.0-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- BDU:2026-04360
- GHSA-752w-5fwx-jx9f
- ALSA-2026:12176
- ALSA-2026:13916
- openSUSE-SU-2026:10397-1
- openSUSE-SU-2026:10681-1
- openSUSE-SU-2026:20431-1
- PYSEC-2026-120
- RHSA-2026:12176
- RHSA-2026:13508
- RHSA-2026:13512
- RHSA-2026:13672
- RHSA-2026:13916
- RHSA-2026:17083
- RHSA-2026:19138
- RHSA-2026:19355
- RHSA-2026:21431
- RHSA-2026:21517
- RHSA-2026:22330
- RLSA-2026:12176
- Published
- Mar 13, 2026
- Updated
- Sep 10, 2026
- EPSS
- 0.2% · 20th percentile
- CWE
- CWE-345
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| pyjwt project | pyjwt | cpe:2.3:a:pyjwt_project:pyjwt |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- pyjwt project pyjwtbefore 2.12.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
jpadilla pyjwt
- < 2.12.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | fence-agents-amt-ws | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-apc | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-apc-snmp | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-bladecenter | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-brocade | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-cisco-mds | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-cisco-ucs | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-drac5 | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-eaton-snmp | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-emerson | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-eps | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-heuristics-ping | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-hpblade | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-ibm-powervs | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-ibm-vpc | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-ibmblade | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-ifmib | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-ilo-moonshot | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-ilo-mp | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-ilo-ssh | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-ilo2 | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-intelmodular | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-ipdu | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
| AlmaLinux:10 | fence-agents-ipmilan | before 4.16.0-13.el10_1.4 | 4.16.0-13.el10_1.4 |
+96
Same product
pyjwt project: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-102268PyJWT: Asymmetric-PEM detection bypass: whitespace/line-ending-mutated public keys skip the HS/asymmetric confusion guard36Monitor
- CVE-2026-102267PyJWT: PyJWKClient follows redirects when fetching JWKS36Monitor
- CVE-2026-102266PyJWK accepts empty HMAC keys, bypassing PyJWT's empty-key validation36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-53861Nov 29, 2024 · Issuer field partial matches allowed in pyjwt30Monitor
- ← EarlierCVE-2025-45768Jul 31, 2025 · pyjwt v2.10.1 was discovered to contain weak encryption.28Monitor
- Later →CVE-2026-48522May 28, 2026 · PyJWKClient: missing scheme allowlist enables SSRF + token forgery via file://, ftp://, data: schemes16Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| jpadilla pyjwt | 2.12.0 · description | Vendor (CNA) |
| azl3 python-jwt 2.8.0-2 on Azure Linux 3.0 | 2.13.0-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:fence-agents-aliyun | 4.2.1-129.el8_10.25 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:fence-agents-all | 4.2.1-129.el8_10.25 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:fence-agents-amt-ws | 4.2.1-129.el8_10.25 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:fence-agents-apc | 4.2.1-129.el8_10.25 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:fence-agents-apc-snmp | 4.2.1-129.el8_10.25 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:fence-agents-aws | 4.2.1-129.el8_10.25 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:fence-agents-azure-arm | 4.2.1-129.el8_10.25 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:fence-agents-bladecenter | 4.2.1-129.el8_10.25 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:fence-agents-brocade | 4.2.1-129.el8_10.25 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:fence-agents-cisco-mds | 4.2.1-129.el8_10.25 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:fence-agents-cisco-ucs | 4.2.1-129.el8_10.25 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:fence-agents-common | 4.2.1-129.el8_10.25 · AlmaLinux:8 | Package registry (OSV) |
| debian:pyjwt | 2.6.0-1+deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:python-PyJWT | 2.8.0-150400.8.10.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:python-social-auth-core | 4.8.7-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| PyPI:pyjwt | 2.12.0 | Package registry (OSV) |
| red hat:fence-agents | 0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:fence-agents-aliyun-debuginfo | 0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:fence-agents-all | 0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:fence-agents-amt-ws | 0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:fence-agents-apc | 0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:fence-agents-apc-snmp | 0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:fence-agents-azure-arm-debuginfo | 0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:fence-agents-bladecenter | 0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:fence-agents-brocade | 0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:fence-agents-cisco-mds | 0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:fence-agents-cisco-ucs | 0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:fence-agents-common | 0:4.2.1-129.el8_10.25 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
+3
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-102275199 days apartPyJWT accepts inconsistent OKP x/d JWKs, causing public/private key identity confusion32Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-345 · Insufficient Verification of Data AuthenticityCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- JSON Hijacking (aka JavaScript Hijacking)CAPEC-111likelihood: High · High
- Cache PoisoningCAPEC-141likelihood: High · High
- DNS Cache PoisoningCAPEC-142likelihood: High · High
- Content SpoofingCAPEC-148likelihood: Medium · Medium
- Spoofing of UDDI/ebXML MessagesCAPEC-218Medium
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
- Application API Navigation RemappingCAPEC-386Medium
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- access.redhat.com/errata/RHSA-2026:10140
- access.redhat.com/errata/RHSA-2026:10141
- access.redhat.com/errata/RHSA-2026:10184
- access.redhat.com/errata/RHSA-2026:12176
- access.redhat.com/errata/RHSA-2026:13508
- access.redhat.com/errata/RHSA-2026:13512
- access.redhat.com/errata/RHSA-2026:13545
- access.redhat.com/errata/RHSA-2026:13553
- access.redhat.com/errata/RHSA-2026:13672
- access.redhat.com/errata/RHSA-2026:13916
- access.redhat.com/errata/RHSA-2026:17083
- access.redhat.com/errata/RHSA-2026:19138
- access.redhat.com/errata/RHSA-2026:19355
- access.redhat.com/errata/RHSA-2026:19375
- access.redhat.com/errata/RHSA-2026:19712
- access.redhat.com/errata/RHSA-2026:21431
- access.redhat.com/errata/RHSA-2026:21517
- access.redhat.com/errata/RHSA-2026:22330
- access.redhat.com/errata/RHSA-2026:24977
Vendor advisories and official records. Exploit/PoC links are deliberately left out.