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.
CVE-2026-103001
MEDIUMPre-NVD 6.56.5—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 6.5 from GitHub Security Advisory published 2026-09-30. A secondary CVSS source baseline 6.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.5Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 6.5
- EG Score
- 6.5MEDIUMhigh confidence
- EG Risk
- 34EG Risk 34/100CISA SSVC
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 computedSeverity65% × 45%Exploitation0% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.2%
- EPSS %ILE
- 13th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 30, 2026
Last Modified
October 1, 2026
Advisory Details (3)
Auto-updated Sep 30, 2026🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github_commit Patch Available
commit 0c87c8c8b1a7 (jpadilla/pyjwt)
Patch available: jpadilla/pyjwt 2.14.0 (contains commit 0c87c8c8b1a7)
https://github.com/jpadilla/pyjwt/commit/0c87c8c8b1a74cac99ad8115f3050efcb7fbed35generic
PyJWT.decode_complete() method changing provided options object · Issue #679 · jpadilla/pyjwt · GitHub
https://github.com/jpadilla/pyjwt/issues/679github Patch Available🟡 PoC Available
PyJWT.decode() reintroduces options-dict mutation, enabling silent claim-verification bypass on dict reuse (regression of #679) · Advisory · jpadilla/pyjwt · GitHub
https://github.com/jpadilla/pyjwt/security/advisories/GHSA-gvp8-978c-rx2qVendor Advisories for CVE-2026-103001(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| pip | PyJWT | — | ghsa |
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
(2 across 2 ecosystems)
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| pyjwt | 2.10.1-2 ... 2.13.0-1 (6 versions) |
| — |
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| pyjwt | 2.11.0, 2.12.0, 2.12.1, 2.13.0 |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 15× in last 7d / 15× 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.
- 2026-10-04 23:21 UTCEPSS rescore
- 2026-10-04 19:30 UTCGHSA enrichment
- 2026-10-03 21:17 UTCEG score recompute
- 2026-10-03 21:17 UTCGHSA enrichment
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-02 23:05 UTCEG score recompute
- 2026-10-02 23:04 UTCGHSA enrichment
- 2026-10-02 00:49 UTCEG score recompute
- 2026-10-02 00:49 UTCGHSA enrichment
- 2026-10-01 19:49 UTCEPSS rescore
- 2026-10-01 02:34 UTCEG score recompute
- 2026-10-01 02:34 UTCGHSA enrichment
- 2026-09-30 22:27 UTCEG score recompute
- 2026-09-30 21:32 UTCEG score recompute
- 2026-09-30 21:30 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-103001?
CVE-2026-103001 is a medium vulnerability published on September 30, 2026. PyJWT is a Python implementation of JSON Web Token standards. From 2.11.0 through 2.13.0, PyJWT's PyJWT.mergeoptions() method can modify a caller-supplied mutable options mapping when verifysignature is false. If an application reuses that same mapping for a later decode() or decodecomplete() call…
When was CVE-2026-103001 disclosed?
CVE-2026-103001 was first published on September 30, 2026, with the most recent update on October 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-103001 actively exploited?
CVE-2026-103001 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-103001?
CVE-2026-103001 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-103001?
A fix for CVE-2026-103001 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-103001 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-103001
Is Your Infrastructure Affected by CVE-2026-103001?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.