PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT get_signing_key_from_jwt is affected because unknown kid misses force refreshes without a negative cache or minimum refresh interval. This occurs when unauthenticated tokens repeatedly use the same unknown kid or varying kid values absent from the cached JWKS. As a result, each cache miss causes PyJWKClient to refresh the JWKS. Consequently, attacker traffic can amplify outbound requests to the configured JWKS endpoint. This issue is fixed in version 2.14.0.
CVE-2026-101917
“—” beside the score: it is equal to NVD's CVSS score.
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4% (37th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 5.3 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-09-29) is not newer than that change (2026-10-07), so it does not.
Also known asEUVD-2026-88478 (ENISA EUVD) · GHSA-2gx3-rcp4-g85q (GitHub Security Advisories)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHmedium confidence
- EG Risk
- 65EG Risk 65/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)Severity75% × 45%Impact severity (EG Severity): CVSS 7.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.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.4%
- EPSS %ILE
- 37th
- 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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; 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 public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 28, 2026
Last Modified
October 7, 2026
Advisory Details (3)
Auto-updated Sep 28, 20262.14.0
Patch available: jpadilla/pyjwt 2.14.0
https://github.com/jpadilla/pyjwt/releases/tag/2.14.0commit ba4853a75fb9 (jpadilla/pyjwt)
Patch available: jpadilla/pyjwt 2.14.0 (contains commit ba4853a75fb9)
https://github.com/jpadilla/pyjwt/commit/ba4853a75fb9676362da17f67d0f64bd18afd4e1PyJWKClient still amplifies unauthenticated JWKS fetches on unknown kid values (incomplete fix of CVE-2026-48524) · Advisory · jpadilla/pyjwt · GitHub
https://github.com/jpadilla/pyjwt/security/advisories/GHSA-2gx3-rcp4-g85qVendor Advisories for CVE-2026-101917(9)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:92452Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Enterprise Linux AI 3.5.2 enhancement update
- RHSA-2026:92449Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Enterprise Linux AI 3.5.2 enhancement update
- RHSA-2026:82415Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat AI Inference 3.5.2 (cpu)
- RHSA-2026:82371Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat AI Inference 3.5.2 (spyre)
- RHSA-2026:82368Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat AI Inference 3.5.2 (cuda)
- RHSA-2026:82061Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat AI Inference Tech Preview 3.5.2 (Gaudi)
- RHSA-2026:82059Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat AI Inference 3.5.2 (ROCm)
- CVE-2026-101917Microsoft Security Response Center (MSRC)Medium
PyJWT: PyJWKClient still amplifies unauthenticated JWKS fetches on unknown kid values (incomplete fix of CVE-2026-48524)
- +1 more
Patch Availability(9)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | rhelai3/bootc-rocm-rhel9:1793135863 | 2026-10-29 | redhat |
| redhat | rhelai3/disk-image-cuda-rhel9:1793206758 | 2026-10-29 | redhat |
| ubuntu | python3-jwt (1.5.3+ds1-1ubuntu0.1+esm4) @ bionic | 2026-10-24 | ubuntu |
| redhat | rhaii/vllm-rocm-rhel9:1791425869 | 2026-10-13 | redhat |
| redhat | rhaii/vllm-gaudi-rhel9:1791427182 | 2026-10-13 | redhat |
| redhat | rhaii/vllm-cpu-rhel9:1791473614 | 2026-10-13 | redhat |
| redhat | rhaii/vllm-cuda-rhel9:1791473631 | 2026-10-13 | redhat |
| redhat | rhaii/vllm-spyre-rhel9:1791818357 | 2026-10-13 | redhat |
| pip | pyjwt @ 2.14.0 (fixes <= 2.13.0) | — | 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
(4 across 4 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| pyjwt | 2.10.1-1 ... 2.7.0-1 (13 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| pyjwt | 2.10.1-2 ... 2.15.1-1 (10 versions) |
| — |
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 | 0.1.1 ... 2.9.0 (55 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
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 11× 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.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 81 is merged into the row it repeats.
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-11-01 08:00 UTCGHSA enrichmentGHSA-2gx3-rcp4-g85q · GitHub severity MODERATE · GitHub CVSS 5.3
- 2026-11-01 08:00 UTCEG score recompute
- 2026-10-31 17:19 UTCEG score recompute
- 2026-10-31 17:19 UTCVendor advisory
- 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-25 14:57 UTCEG score recompute
- 2026-10-24 18:36 UTCEG score recompute
- 2026-10-24 18:36 UTCVendor advisory
- 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-18 05:11 UTCEG score recompute
- 2026-10-17 19:54 UTCEG score recompute
- 2026-10-17 19:54 UTCVendor advisory
Show 55 moreShow fewer
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-12 16:41 UTCEG score recompute
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-11 20:16 UTCEG score recompute
- 2026-10-11 18:48 UTCVendor advisory
- 2026-10-11 18:28 UTCEG score recompute
- 2026-10-11 15:02 UTCEG score recompute
- 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-11 07:06 UTCEG score recompute
- 2026-10-11 07:06 UTCVendor advisory
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-10 07:27 UTCEG score recompute
- 2026-10-10 07:27 UTCVendor advisory
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-09 19:45 UTCVendor advisory
- 2026-10-09 08:05 UTCVendor advisory
- 2026-10-08 20:24 UTCEG score recompute
- 2026-10-08 20:24 UTCVendor advisory
- 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-08 08:43 UTCEG score recompute
- 2026-10-08 08:43 UTCVendor advisory
- 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 26th percentile
- 2026-10-07 21:02 UTCEG score recompute▲ 2.20
- 2026-10-07 21:02 UTCVendor advisory
- 2026-10-07 21:02 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
- 2026-10-07 14:55 UTCVendor advisory
- 2026-10-06 15:39 UTCEG score recompute
- 2026-10-06 15:39 UTCVendor advisory
- 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 26th percentile
- 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 26th percentile
- 2026-10-05 16:11 UTCEG score recompute
- 2026-10-05 16:11 UTCVendor advisory
- 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 26th percentile
- 2026-10-04 16:49 UTCVendor advisory
- 2026-10-03 17:31 UTCEG score recompute
- 2026-10-03 17:31 UTCVendor advisory
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 26th percentile
- 2026-10-02 18:16 UTCVendor advisory
- 2026-10-02 18:16 UTCEG score recompute
- 2026-10-02 18:16 UTCVendor advisory
- 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 26th percentile
- 2026-10-01 19:00 UTCVendor advisory
- 2026-09-30 19:44 UTCEG score recompute
- 2026-09-30 19:44 UTCVendor advisory
- 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 26th percentile
- 2026-09-29 23:45 UTCEG score recompute
- 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 26th percentile
- 2026-09-28 21:18 UTCEG score recompute
- 2026-09-28 20:46 UTCEG score recompute
- 2026-09-28 20:26 UTCEG score recomputeFirst assessed: 5.3 MEDIUM
- 2026-09-28 20:26 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownDebian:12:pyjwt
Same vendor
10 shownredhat:RHSA-2026:82059
Frequently asked(5)
What is CVE-2026-101917?
When was the CVE record for CVE-2026-101917 published?
Is CVE-2026-101917 actively exploited?
What is the CVSS score of CVE-2026-101917?
How do I remediate CVE-2026-101917?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-101917
Is Your Infrastructure Affected by CVE-2026-101917?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.