CVE-2026-103001: PyJWT.decode() reintroduces options-dict mutation, enabling silent claim-verification bypass on dict reuse
Noroxi assessment
Priority: Monitor (action score 26/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.25% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: azl3 python-jwt 2.13.0-1 on Azure Linux 3.0 2.15.1-1.
Low priority for now. Upgrade to azl3 python-jwt 2.13.0-1 on Azure Linux 3.0 2.15.1-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 Python implementation of JSON Web Token standards. From 2.11.0 through 2.13.0, PyJWT's PyJWT._merge_options() method can modify a caller-supplied mutable options mapping when verify_signature is false. If an application reuses that same mapping for a later decode() or decode_complete() call and changes verify_signature to true, the mapping can retain false values for expiration, not-before, issued-at, audience, issuer, subject, and JWT ID checks. A signed token with invalid registered claims can then be accepted without disabling signature verification, but applications that create a fresh options mapping for each call are not affected.
- Published
- Sep 30, 2026
- Updated
- Oct 8, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- CWE-471
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 6.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.
Is your version affected? Check itNoroxi 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 |
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.11.0, <= 2.13.0affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- pyjwt project pyjwt2.11.0 and later · before 2.13.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:14 | pyjwt | before 2.14.0-1 | 2.14.0-1 |
| openSUSE:Leap 16.0 | python-PyJWT | before 2.12.1-160000.3.1 | 2.12.1-160000.3.1 |
| openSUSE:Tumbleweed | python-PyJWT | before 2.15.1-1.1 | 2.15.1-1.1 |
| PyPI | pyjwt | from 2.11.0 · up to and including 2.13.0 | — |
| SUSE:Linux Micro 6.1 | python-PyJWT | before 2.12.1-slfo.1.1_3.1 | 2.12.1-slfo.1.1_3.1 |
| SUSE:Linux Micro 6.2 | python-PyJWT | before 2.12.1-160000.3.1 | 2.12.1-160000.3.1 |
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-2026-102273Sep 28, 2026 · PyJWT accepts public JWK containers as HMAC secrets29Monitor
- ← EarlierCVE-2026-102274Sep 28, 2026 · PyJWT: Malformed RSA JWK aborts parsing of an entire JWK Set30Monitor
- ← EarlierCVE-2026-102275Sep 28, 2026 · PyJWT accepts inconsistent OKP x/d JWKs, causing public/private key identity confusion32Monitor
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 |
|---|---|---|
| azl3 python-jwt 2.13.0-1 on Azure Linux 3.0 | 2.15.1-1 · Release Notes | Microsoft (MSRC) |
| debian:pyjwt | 2.14.0-1 · Debian:14 | Package registry (OSV) |
| opensuse:python-PyJWT | 2.15.1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:python-PyJWT | 2.12.1-160000.3.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
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.
- Published
- Fix recorded+4 d
- TodayNov 13, 2026+44 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: researcher credit · variant or chain candidate · public bounty program.
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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-471 · Modification of Assumed-Immutable Data (MAID)CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/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)
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
- Application API Navigation RemappingCAPEC-386Medium
- Navigation Remapping To Propagate Malicious ContentCAPEC-387Medium
- Application API Button HijackingCAPEC-388Medium
ATT&CK techniques
—
Change log (2)
- Fix✗ → ✓
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.