CVE-2026-102271

HIGHPre-NVD 7.47.4
EchelonGraph scoreMEDIUM confidence

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

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-09-29. A secondary CVSS source baseline 7.4; 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-88539 (ENISA EUVD) · GHSA-p4g4-x82p-q773 (GitHub Security Advisories)Source: ENISA EUVD

7.4EG
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.2%CVSS: 7.4Exploit: 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.4.0 until 2.14.0, PyJWT HMACAlgorithm.prepare_key is affected because asymmetric-key guard relies on textual markers that are absent from DER encoding. This occurs when an application mixes HMAC and asymmetric algorithms and supplies a DER public key as the shared verification key. As a result, PyJWT uses public DER bytes as an HMAC secret. Consequently, an attacker who knows the public key can forge authenticated HMAC tokens. This issue is fixed in version 2.14.0.

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.2%
EPSS %ILE
11th
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.4): severity, escalated by confirmed exploitation. This CVE's 7.4 is its impact severity (EG Severity), not escalated.

EG Severity
7.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 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, Track* at medium and Attend at high mission impact.

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 no (CISA Vulnrichment) · Technical impact total (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; 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 total (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 2798504fa266 (jpadilla/pyjwt)

Patch available: jpadilla/pyjwt 2.14.0 (contains commit 2798504fa266)

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

Public keys in DER form are accepted as HMAC secrets, bypassing the CVE-2022-29217 guard · Advisory · jpadilla/pyjwt · GitHub

https://github.com/jpadilla/pyjwt/security/advisories/GHSA-p4g4-x82p-q773

Patch Availability(14)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-jwt (1.7.1-2ubuntu2.1+esm3) @ focal2026-10-30ubuntu
ubuntupython3-jwt (2.13.0-1ubuntu1) @ stonking2026-10-30ubuntu
redhatrhelai3/bootc-rocm-rhel9:17931358632026-10-29redhat
redhatrhoai/odh-trustyai-garak-lls-provider-dsp-rhel9:17927985522026-10-29redhat
redhatrhelai3/disk-image-cuda-rhel9:17932067582026-10-29redhat
redhatansible-automation-platform-27/metrics-service-rhel9:17923872162026-10-21redhat
redhatansible-automation-platform-tech-preview/metrics-service-rhel9:17919448192026-10-21redhat
redhatpython3.12-pyjwt-0:2.14.0-1.el9ap2026-10-21redhat
redhatrhaii/vllm-spyre-rhel9:17918183572026-10-13redhat
redhatrhaii/vllm-cuda-rhel9:17914736312026-10-13redhat
redhatrhaii/vllm-rocm-rhel9:17914258692026-10-13redhat
redhatrhaii/vllm-gaudi-rhel9:17914271822026-10-13redhat
redhatrhaii/vllm-cpu-rhel9:17914736142026-10-13redhat
pippyjwt @ 2.14.0 (fixes >= 2.4.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.10.0 ... 2.9.0 (12 versions)
  • 2.4.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.

Additional Vendor Advisories

(2)

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 / 70× 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.2% · 11th percentile
  2. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-p4g4-x82p-q773 · GitHub severity HIGH · GitHub CVSS 7.4
  3. 2026-11-01 08:00 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  5. 2026-10-30 20:42 UTCEG score recompute
  6. 2026-10-30 20:42 UTCVendor advisory
  7. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  8. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  10. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  11. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  12. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  13. 2026-10-25 14:56 UTCEG score recompute
  14. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-10-24 08:17 UTCEG score recompute
  16. 2026-10-24 08:17 UTCVendor advisory
  17. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  21. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  22. 2026-10-18 05:10 UTCEG score recompute
  23. 2026-10-17 19:51 UTCEG score recompute
  24. 2026-10-17 19:51 UTCVendor advisory
  25. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
Show 63 more
  1. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  2. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  3. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  4. 2026-10-12 16:41 UTCEG score recompute
  5. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  6. 2026-10-11 21:24 UTCVendor advisory
  7. 2026-10-11 20:16 UTCEG score recompute
  8. 2026-10-11 18:28 UTCEG score recompute
  9. 2026-10-11 15:02 UTCEG score recompute
  10. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  11. 2026-10-11 10:18 UTCVendor advisory
  12. 2026-10-10 23:15 UTCEG score recompute
  13. 2026-10-10 23:15 UTCVendor advisory
  14. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-10-10 12:12 UTCVendor advisory
  16. 2026-10-10 01:10 UTCEG score recompute
  17. 2026-10-10 01:09 UTCVendor advisory
  18. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-10-09 14:07 UTCVendor advisory
  20. 2026-10-09 03:04 UTCEG score recompute
  21. 2026-10-09 03:04 UTCVendor advisory
  22. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-10-08 16:01 UTCVendor advisory
  24. 2026-10-08 04:33 UTCEG score recompute
  25. 2026-10-08 04:33 UTCVendor advisory
  26. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  27. 2026-10-07 17:31 UTCVendor advisory
  28. 2026-10-07 05:54 UTCVendor advisory
  29. 2026-10-06 18:51 UTCVendor advisory
  30. 2026-10-06 17:14 UTCEG score recompute
  31. 2026-10-06 17:14 UTCVendor advisory
  32. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  33. 2026-10-06 06:12 UTCVendor advisory
  34. 2026-10-05 18:53 UTCEG score recompute
  35. 2026-10-05 18:53 UTCVendor advisory
  36. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  37. 2026-10-05 07:51 UTCEG score recompute
  38. 2026-10-05 07:51 UTCVendor advisory
  39. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  40. 2026-10-04 20:49 UTCVendor advisory
  41. 2026-10-04 09:47 UTCVendor advisory
  42. 2026-10-03 22:43 UTCEG score recompute
  43. 2026-10-03 22:43 UTCVendor advisory
  44. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  45. 2026-10-03 11:40 UTCVendor advisory
  46. 2026-10-03 00:33 UTCEG score recompute
  47. 2026-10-03 00:33 UTCVendor advisory
  48. 2026-10-02 13:30 UTCVendor advisory
  49. 2026-10-02 02:26 UTCEG score recompute
  50. 2026-10-02 02:26 UTCVendor advisory
  51. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  52. 2026-10-01 15:23 UTCEG score recompute
  53. 2026-10-01 15:23 UTCVendor advisory
  54. 2026-10-01 15:06 UTCEG score recompute
  55. 2026-10-01 15:06 UTCVendor advisory
  56. 2026-09-30 17:31 UTCEG score recompute
  57. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  58. 2026-09-29 19:27 UTCEG score recompute
  59. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  60. 2026-09-29 08:20 UTCEG score recompute
  61. 2026-09-28 21:18 UTCEG score recompute
  62. 2026-09-28 20:36 UTCEG score recomputeFirst assessed: 7.4 HIGH
  63. 2026-09-28 20:36 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-102271?
CVE-2026-102271 is a high-severity vulnerability; its CVE record was published on September 28, 2026. PyJWT is a Python implementation of JSON Web Token standards. From 2.4.0 until 2.14.0, PyJWT HMACAlgorithm.prepare_key is affected because asymmetric-key guard relies on textual markers that are absent from DER encoding. This occurs when an application mixes HMAC and asymmetric algorithms and…
When was the CVE record for CVE-2026-102271 published?
The CVE record for CVE-2026-102271 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-102271 actively exploited?
CVE-2026-102271 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102271?
CVE-2026-102271 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102271?
A fix for CVE-2026-102271 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102271 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-102271

Explore →

Is Your Infrastructure Affected by CVE-2026-102271?

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