CVE-2026-102270

MEDIUMNVD 4.94.9
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.9 under NVD CVSS v3. EPSS exploit probability: 0.2% (15th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 4.4 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-30) is not newer than that change (2026-10-06), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2026-88537 (ENISA EUVD) · GHSA-jwrc-g2q2-pq5p (GitHub Security Advisories) · PYSEC-2026-4148 (OSV.dev)Source: ENISA EUVD

4.9EG
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.2%CVSS: 4.9Exploit: 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 is_pem_format is affected because lazy PEM regular expression backtracks extensively. This occurs when a certificate-like input contains repeated BEGIN markers without a matching END marker. As a result, is_pem_format performs unbounded backtracking while searching for a PEM end marker. Consequently, an attacker can cause intensive CPU consumption. This issue is fixed in version 2.14.0.

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

EG Severity
4.9 MEDIUMCVSS-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.2% 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; 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 28, 2026

Last Modified

October 6, 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 8b4e233a2220 (jpadilla/pyjwt)

Patch available: jpadilla/pyjwt 2.14.0 (contains commit 8b4e233a2220)

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

ReDoS vulnerability when calling the `is_pem_format` function. · Advisory · jpadilla/pyjwt · GitHub

https://github.com/jpadilla/pyjwt/security/advisories/GHSA-jwrc-g2q2-pq5p

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
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
redhatrhaii/vllm-rocm-rhel9:17914258692026-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.

Data Freshness Timeline

(refreshed 6× in last 7d / 32× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  2. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  3. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  4. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  5. 2026-11-09 16:33 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  6. 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  7. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  8. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  9. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  10. 2026-11-03 16:45 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  11. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  12. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  13. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-jwrc-g2q2-pq5p · GitHub severity MODERATE · GitHub CVSS 4.4
  14. 2026-11-01 08:00 UTCEchelonGraph re-scored
  15. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  16. 2026-10-31 12:25 UTCOSV refresh
  17. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  18. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  19. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  20. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  21. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  22. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  23. 2026-10-25 14:56 UTCEchelonGraph re-scored
  24. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  25. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
Show 58 more
  1. 2026-10-23 09:29 UTCEchelonGraph re-scored
  2. 2026-10-23 09:29 UTCVendor advisory
  3. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-18 05:10 UTCEchelonGraph re-scored
  9. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-12 16:41 UTCEchelonGraph re-scored
  15. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-10-12 01:40 UTCVendor advisory
  17. 2026-10-11 20:16 UTCEchelonGraph re-scored
  18. 2026-10-11 18:28 UTCEchelonGraph re-scored
  19. 2026-10-11 15:02 UTCEchelonGraph re-scored
  20. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-10-11 00:20 UTCEchelonGraph re-scored
  22. 2026-10-11 00:20 UTCVendor advisory
  23. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-10-09 23:00 UTCEchelonGraph re-scored
  25. 2026-10-09 23:00 UTCVendor advisory
  26. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  27. 2026-10-08 21:39 UTCEchelonGraph re-scored
  28. 2026-10-08 21:39 UTCVendor advisory
  29. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  30. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  31. 2026-10-07 20:11 UTCVendor advisory
  32. 2026-10-06 18:51 UTCEchelonGraph re-scored▲ 0.50
  33. 2026-10-06 18:51 UTCVendor advisory
  34. 2026-10-06 18:51 UTCNVD updateCVSS v3 → 4.9
  35. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  36. 2026-10-06 02:24 UTCEchelonGraph re-scored
  37. 2026-10-06 02:24 UTCVendor advisory
  38. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  39. 2026-10-05 01:04 UTCEchelonGraph re-scored
  40. 2026-10-05 01:04 UTCVendor advisory
  41. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  42. 2026-10-03 23:44 UTCEchelonGraph re-scored
  43. 2026-10-03 23:44 UTCVendor advisory
  44. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  45. 2026-10-02 22:23 UTCEchelonGraph re-scored
  46. 2026-10-02 22:23 UTCVendor advisory
  47. 2026-10-01 21:03 UTCEchelonGraph re-scored
  48. 2026-10-01 21:03 UTCVendor advisory
  49. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  50. 2026-09-30 19:44 UTCEchelonGraph re-scored
  51. 2026-09-30 19:44 UTCVendor advisory
  52. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  53. 2026-09-29 20:31 UTCEchelonGraph re-scored
  54. 2026-09-29 19:44 UTCEchelonGraph re-scored
  55. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  56. 2026-09-28 21:18 UTCEchelonGraph re-scored
  57. 2026-09-28 20:36 UTCEchelonGraph re-scoredFirst assessed: 4.4 MEDIUM
  58. 2026-09-28 20:36 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-102270?
CVE-2026-102270 is a medium-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 is_pem_format is affected because lazy PEM regular expression backtracks extensively. This occurs when a certificate-like input contains repeated BEGIN markers without a matching END marker. As a result,…
When was the CVE record for CVE-2026-102270 published?
The CVE record for CVE-2026-102270 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 6, 2026; the record at its source may have been updated since.
Is CVE-2026-102270 actively exploited?
CVE-2026-102270 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102270?
CVE-2026-102270 has a CVSS v3 base score of 4.9 (NVD).
How do I remediate CVE-2026-102270?
A fix for CVE-2026-102270 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102270 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-102270

Explore →

Is Your Infrastructure Affected by CVE-2026-102270?

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