CVE-2026-102265

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

Score 5.3 from GitHub Security Advisory (severity: MODERATE) published 2026-09-29. A secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-88549 (ENISA EUVD) · GHSA-8wjv-2p76-3863 (GitHub Security Advisories) · PYSEC-2026-4142 (OSV.dev)Source: ENISA EUVD

5.3EG
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.3%CVSS: 5.3Exploit: 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.13.0 until 2.14.0, PyJWS._load in jwt/api_jws.py is affected because parser catches ValueError but not RecursionError. This occurs when a deeply nested token header reaches json.loads. As a result, RecursionError escapes the documented PyJWT error hierarchy. Consequently, an unauthenticated malformed token can cause a request-level failure and HTTP 500. This issue is fixed in version 2.14.0.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
55
EG Risk 55/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)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 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.3%
EPSS %ILE
27th
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 (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 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-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_commit, github_release, github.
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 06573692ebcd (jpadilla/pyjwt)

Patch available: jpadilla/pyjwt 2.14.0 (contains commit 06573692ebcd)

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

Uncaught RecursionError in jwt.decode() on deeply nested token header · Advisory · jpadilla/pyjwt · GitHub

https://github.com/jpadilla/pyjwt/security/advisories/GHSA-8wjv-2p76-3863

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhaii/vllm-rocm-rhel9:17914258692026-10-13redhat
redhatrhaii/vllm-gaudi-rhel9:17914271822026-10-13redhat
redhatrhaii/vllm-cuda-rhel9:17914736312026-10-13redhat
redhatrhaii/vllm-spyre-rhel9:17918183572026-10-13redhat
redhatrhaii/vllm-cpu-rhel9:17914736142026-10-13redhat
pippyJWT @ 2.14.0 (fixes >= 2.13.0, < 2.14.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
pyjwt2.13.0
  • 2.13.0 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.

Data Freshness Timeline

(refreshed 10× in last 7d / 53× 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-01 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  2. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-8wjv-2p76-3863 · GitHub severity MODERATE · GitHub CVSS 5.3
  3. 2026-11-01 08:00 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  5. 2026-10-31 12:25 UTCOSV refresh
  6. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  7. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  8. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  12. 2026-10-25 14:56 UTCEG score recompute
  13. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  15. 2026-10-23 09:29 UTCEG score recompute
  16. 2026-10-23 09:29 UTCVendor advisory
  17. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  18. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  19. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  20. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  21. 2026-10-18 05:10 UTCEG score recompute
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  23. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  24. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  25. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
Show 43 more
  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-10-12 16:41 UTCEG score recompute
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  4. 2026-10-11 20:16 UTCEG score recompute
  5. 2026-10-11 18:28 UTCEG score recompute
  6. 2026-10-11 15:02 UTCEG score recompute
  7. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  8. 2026-10-11 03:30 UTCEG score recompute
  9. 2026-10-11 03:30 UTCVendor advisory
  10. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  11. 2026-10-10 01:19 UTCEG score recompute
  12. 2026-10-10 01:19 UTCVendor advisory
  13. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  14. 2026-10-08 23:10 UTCEG score recompute
  15. 2026-10-08 23:10 UTCVendor advisory
  16. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  17. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  18. 2026-10-07 21:02 UTCVendor advisory
  19. 2026-10-07 02:04 UTCEG score recompute
  20. 2026-10-07 02:04 UTCVendor advisory
  21. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  22. 2026-10-05 23:56 UTCEG score recompute
  23. 2026-10-05 23:56 UTCVendor advisory
  24. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  25. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  26. 2026-10-04 21:48 UTCVendor advisory
  27. 2026-10-03 19:40 UTCEG score recompute
  28. 2026-10-03 19:40 UTCVendor advisory
  29. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  30. 2026-10-02 17:32 UTCEG score recompute
  31. 2026-10-02 17:32 UTCVendor advisory
  32. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  33. 2026-10-01 15:23 UTCEG score recompute
  34. 2026-10-01 15:23 UTCVendor advisory
  35. 2026-10-01 15:06 UTCEG score recompute
  36. 2026-10-01 15:06 UTCVendor advisory
  37. 2026-09-30 19:44 UTCEG score recompute
  38. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  39. 2026-09-29 23:45 UTCEG score recompute
  40. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  41. 2026-09-28 21:18 UTCEG score recompute
  42. 2026-09-28 20:58 UTCEG score recomputeFirst assessed: 5.3 MEDIUM
  43. 2026-09-28 20:57 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-102265?
CVE-2026-102265 is a medium-severity vulnerability; its CVE record was published on September 28, 2026. PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, PyJWS._load in jwt/api_jws.py is affected because parser catches ValueError but not RecursionError. This occurs when a deeply nested token header reaches json.loads. As a result, RecursionError escapes the…
When was the CVE record for CVE-2026-102265 published?
The CVE record for CVE-2026-102265 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-102265 actively exploited?
CVE-2026-102265 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102265?
CVE-2026-102265 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102265?
A fix for CVE-2026-102265 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102265 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-102265

Explore →

Is Your Infrastructure Affected by CVE-2026-102265?

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