CVE-2026-103001

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this weekElevated

Also known asEUVD-2026-90388 (ENISA EUVD) · GHSA-gvp8-978c-rx2q (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
17th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 30, 2026

Last Modified

October 8, 2026

Advisory Details (3)

Auto-updated Sep 30, 2026
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/0c87c8c8b1a74cac99ad8115f3050efcb7fbed35
Web page

PyJWT.decode_complete() method changing provided options object · Issue #679 · jpadilla/pyjwt · GitHub

https://github.com/jpadilla/pyjwt/issues/679
GitHub advisoryMentions a patch (unverified)

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-rx2q

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhelai3/disk-image-cuda-rhel9:17932067582026-10-29redhat
redhatrhelai3/bootc-rocm-rhel9:17931358632026-10-29redhat
redhatrhaii/vllm-cpu-rhel9:17914736142026-10-13redhat
redhatrhaii/vllm-rocm-rhel9:17914258692026-10-13redhat
redhatrhaii/vllm-gaudi-rhel9:17914271822026-10-13redhat
redhatrhaii/vllm-spyre-rhel9:17918183572026-10-13redhat
redhatrhaii/vllm-cuda-rhel9:17914736312026-10-13redhat
pipPyJWT—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)
PackageVulnerable rangeFix by version rangeDependents
pyjwt2.10.1-2 ... 2.13.0-1 (6 versions)
  • every version up to 2.14.0-1: fixed in 2.14.0-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pyjwt2.11.0, 2.12.0, 2.12.1, 2.13.0
  • 2.11.0 through 2.13.0: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 66× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  3. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  4. 2026-10-30 23:54 UTCEG score recompute
  5. 2026-10-30 23:54 UTCVendor advisory
  6. 2026-10-30 23:54 UTCGHSA enrichmentGHSA-gvp8-978c-rx2q · GitHub CVSS 6.5
  7. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  8. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  9. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  10. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  11. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  12. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  13. 2026-10-25 14:56 UTCEG score recompute
  14. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  16. 2026-10-23 09:27 UTCEG score recompute
  17. 2026-10-23 09:27 UTCVendor advisory
  18. 2026-10-23 09:27 UTCGHSA enrichmentGHSA-gvp8-978c-rx2q · GitHub CVSS 6.5
  19. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  20. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  21. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  22. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  23. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  24. 2026-10-18 05:10 UTCEG score recompute
  25. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
Show 54 more
  1. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  2. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  3. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  4. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  5. 2026-10-12 16:40 UTCEG score recompute
  6. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  7. 2026-10-11 20:15 UTCEG score recompute
  8. 2026-10-11 18:28 UTCEG score recompute
  9. 2026-10-11 15:01 UTCEG score recompute
  10. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  11. 2026-10-11 08:08 UTCEG score recompute
  12. 2026-10-11 08:08 UTCVendor advisory
  13. 2026-10-11 08:08 UTCGHSA enrichmentGHSA-gvp8-978c-rx2q · GitHub CVSS 6.5
  14. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  15. 2026-10-10 09:54 UTCEG score recompute
  16. 2026-10-10 09:54 UTCVendor advisory
  17. 2026-10-10 09:54 UTCGHSA enrichmentGHSA-gvp8-978c-rx2q · GitHub CVSS 6.5
  18. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  19. 2026-10-09 11:42 UTCEG score recompute
  20. 2026-10-09 11:42 UTCVendor advisory
  21. 2026-10-09 11:42 UTCGHSA enrichmentGHSA-gvp8-978c-rx2q · GitHub CVSS 6.5
  22. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  23. 2026-10-08 13:28 UTCEG score recompute
  24. 2026-10-08 13:28 UTCVendor advisory
  25. 2026-10-08 13:28 UTCGHSA enrichmentGHSA-gvp8-978c-rx2q · GitHub CVSS 6.5
  26. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  27. 2026-10-07 20:51 UTCVendor advisory
  28. 2026-10-07 20:51 UTCGHSA enrichmentGHSA-gvp8-978c-rx2q · GitHub CVSS 6.5
  29. 2026-10-06 22:38 UTCEG score recompute
  30. 2026-10-06 22:38 UTCVendor advisory
  31. 2026-10-06 22:38 UTCGHSA enrichmentGHSA-gvp8-978c-rx2q · GitHub CVSS 6.5
  32. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  33. 2026-10-06 00:26 UTCEG score recompute
  34. 2026-10-06 00:26 UTCGHSA enrichmentGHSA-gvp8-978c-rx2q · GitHub CVSS 6.5
  35. 2026-10-05 23:56 UTCEG score recompute
  36. 2026-10-05 23:56 UTCGHSA enrichmentGHSA-gvp8-978c-rx2q · GitHub CVSS 6.5
  37. 2026-10-05 17:42 UTCEG score recompute
  38. 2026-10-05 17:42 UTCGHSA enrichmentGHSA-gvp8-978c-rx2q · GitHub CVSS 6.5
  39. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  40. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  41. 2026-10-04 19:30 UTCGHSA enrichmentGHSA-gvp8-978c-rx2q · GitHub CVSS 6.5
  42. 2026-10-03 21:17 UTCEG score recompute
  43. 2026-10-03 21:17 UTCGHSA enrichmentGHSA-gvp8-978c-rx2q · GitHub CVSS 6.5
  44. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  45. 2026-10-02 23:05 UTCEG score recompute
  46. 2026-10-02 23:04 UTCGHSA enrichmentGHSA-gvp8-978c-rx2q · GitHub CVSS 6.5
  47. 2026-10-02 00:49 UTCEG score recompute
  48. 2026-10-02 00:49 UTCGHSA enrichmentGHSA-gvp8-978c-rx2q · GitHub CVSS 6.5
  49. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  50. 2026-10-01 02:34 UTCEG score recompute
  51. 2026-10-01 02:34 UTCGHSA enrichmentGHSA-gvp8-978c-rx2q · GitHub CVSS 6.5
  52. 2026-09-30 22:27 UTCEG score recompute
  53. 2026-09-30 21:32 UTCEG score recomputeFirst assessed: 6.5 MEDIUM
  54. 2026-09-30 21:30 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-103001?
CVE-2026-103001 is a medium-severity vulnerability; its CVE record was 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._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()…
When was the CVE record for CVE-2026-103001 published?
The CVE record for CVE-2026-103001 was published on September 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-103001 actively exploited?
CVE-2026-103001 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th 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

Explore →

Is Your Infrastructure Affected by CVE-2026-103001?

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