CVE-2026-101917

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” 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.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — Patch released this weekElevated

Also known asEUVD-2026-88478 (ENISA EUVD) · GHSA-2gx3-rcp4-g85q (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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.4%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG 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, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

2.14.0

Patch available: jpadilla/pyjwt 2.14.0

https://github.com/jpadilla/pyjwt/releases/tag/2.14.0
GitHub commit Patch Available

commit ba4853a75fb9 (jpadilla/pyjwt)

Patch available: jpadilla/pyjwt 2.14.0 (contains commit ba4853a75fb9)

https://github.com/jpadilla/pyjwt/commit/ba4853a75fb9676362da17f67d0f64bd18afd4e1
GitHub advisoryMentions a patch (unverified)

PyJWKClient 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-g85q

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhelai3/bootc-rocm-rhel9:17931358632026-10-29redhat
redhatrhelai3/disk-image-cuda-rhel9:17932067582026-10-29redhat
ubuntupython3-jwt (1.5.3+ds1-1ubuntu0.1+esm4) @ bionic2026-10-24ubuntu
redhatrhaii/vllm-rocm-rhel9:17914258692026-10-13redhat
redhatrhaii/vllm-gaudi-rhel9:17914271822026-10-13redhat
redhatrhaii/vllm-cpu-rhel9:17914736142026-10-13redhat
redhatrhaii/vllm-cuda-rhel9:17914736312026-10-13redhat
redhatrhaii/vllm-spyre-rhel9:17918183572026-10-13redhat
pippyjwt @ 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)
PackageVulnerable rangeFix by version rangeDependents
pyjwt2.10.1-1 ... 2.7.0-1 (13 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pyjwt2.10.1-2 ... 2.15.1-1 (10 versions)
  • every version on: no fix on record
—
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
pyjwt0.1.1 ... 2.9.0 (55 versions)
  • every version up to 2.14.0: fixed in 2.14.0
—

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.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  2. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-2gx3-rcp4-g85q · GitHub severity MODERATE · GitHub CVSS 5.3
  3. 2026-11-01 08:00 UTCEG score recompute
  4. 2026-10-31 17:19 UTCEG score recompute
  5. 2026-10-31 17:19 UTCVendor advisory
  6. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  7. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  8. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  9. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  10. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  11. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  12. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  13. 2026-10-25 14:57 UTCEG score recompute
  14. 2026-10-24 18:36 UTCEG score recompute
  15. 2026-10-24 18:36 UTCVendor advisory
  16. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  17. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  18. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  19. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  20. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  21. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  22. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  23. 2026-10-18 05:11 UTCEG score recompute
  24. 2026-10-17 19:54 UTCEG score recompute
  25. 2026-10-17 19:54 UTCVendor advisory
Show 55 more
  1. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  2. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  4. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  5. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  6. 2026-10-12 16:41 UTCEG score recompute
  7. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-10-11 20:16 UTCEG score recompute
  9. 2026-10-11 18:48 UTCVendor advisory
  10. 2026-10-11 18:28 UTCEG score recompute
  11. 2026-10-11 15:02 UTCEG score recompute
  12. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-10-11 07:06 UTCEG score recompute
  14. 2026-10-11 07:06 UTCVendor advisory
  15. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  16. 2026-10-10 07:27 UTCEG score recompute
  17. 2026-10-10 07:27 UTCVendor advisory
  18. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  19. 2026-10-09 19:45 UTCVendor advisory
  20. 2026-10-09 08:05 UTCVendor advisory
  21. 2026-10-08 20:24 UTCEG score recompute
  22. 2026-10-08 20:24 UTCVendor advisory
  23. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  24. 2026-10-08 08:43 UTCEG score recompute
  25. 2026-10-08 08:43 UTCVendor advisory
  26. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  27. 2026-10-07 21:02 UTCEG score recompute▲ 2.20
  28. 2026-10-07 21:02 UTCVendor advisory
  29. 2026-10-07 21:02 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  30. 2026-10-07 14:55 UTCVendor advisory
  31. 2026-10-06 15:39 UTCEG score recompute
  32. 2026-10-06 15:39 UTCVendor advisory
  33. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  34. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  35. 2026-10-05 16:11 UTCEG score recompute
  36. 2026-10-05 16:11 UTCVendor advisory
  37. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  38. 2026-10-04 16:49 UTCVendor advisory
  39. 2026-10-03 17:31 UTCEG score recompute
  40. 2026-10-03 17:31 UTCVendor advisory
  41. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  42. 2026-10-02 18:16 UTCVendor advisory
  43. 2026-10-02 18:16 UTCEG score recompute
  44. 2026-10-02 18:16 UTCVendor advisory
  45. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  46. 2026-10-01 19:00 UTCVendor advisory
  47. 2026-09-30 19:44 UTCEG score recompute
  48. 2026-09-30 19:44 UTCVendor advisory
  49. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  50. 2026-09-29 23:45 UTCEG score recompute
  51. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  52. 2026-09-28 21:18 UTCEG score recompute
  53. 2026-09-28 20:46 UTCEG score recompute
  54. 2026-09-28 20:26 UTCEG score recomputeFirst assessed: 5.3 MEDIUM
  55. 2026-09-28 20:26 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-101917?
CVE-2026-101917 is a high-severity vulnerability; its CVE record was published on September 28, 2026. 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…
When was the CVE record for CVE-2026-101917 published?
The CVE record for CVE-2026-101917 was published on September 28, 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 7, 2026; the record at its source may have been updated since.
Is CVE-2026-101917 actively exploited?
CVE-2026-101917 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-101917?
CVE-2026-101917 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-101917?
A fix for CVE-2026-101917 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-101917 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-101917

Explore →

Is Your Infrastructure Affected by CVE-2026-101917?

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