CVE-2026-102271

HIGHPre-NVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (6th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this weekElevated
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.4Exploit: Elevated riskExposed 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/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
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
6th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 28, 2026

Last Modified

October 1, 2026

Advisory Details (3)

Auto-updated Sep 28, 2026
🔬 Proof of concept available. 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 Patch Available🟡 PoC Available

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

Vendor Advisories for CVE-2026-102271(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
pyjwt2.10.0 ... 2.9.0 (12 versions)2.14.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 23× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-04 09:47 UTCVendor advisory
  2. 2026-10-03 22:43 UTCEG score recompute
  3. 2026-10-03 22:43 UTCVendor advisory
  4. 2026-10-03 14:25 UTCEPSS rescore
  5. 2026-10-03 11:40 UTCVendor advisory
  6. 2026-10-03 00:33 UTCEG score recompute
  7. 2026-10-03 00:33 UTCVendor advisory
  8. 2026-10-02 13:30 UTCVendor advisory
  9. 2026-10-02 02:26 UTCEG score recompute
  10. 2026-10-02 02:26 UTCVendor advisory
  11. 2026-10-01 19:49 UTCEPSS rescore
  12. 2026-10-01 15:23 UTCEG score recompute
  13. 2026-10-01 15:23 UTCVendor advisory
  14. 2026-10-01 15:06 UTCEG score recompute
  15. 2026-10-01 15:06 UTCVendor advisory
  16. 2026-09-30 17:31 UTCEG score recompute
  17. 2026-09-30 15:02 UTCEPSS rescore
  18. 2026-09-29 19:27 UTCEG score recompute
  19. 2026-09-29 15:20 UTCEPSS rescore
  20. 2026-09-29 08:20 UTCEG score recompute
  21. 2026-09-28 21:18 UTCEG score recompute
  22. 2026-09-28 20:36 UTCEG score recompute
  23. 2026-09-28 20:36 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-102271?
CVE-2026-102271 is a high vulnerability 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 CVE-2026-102271 disclosed?
CVE-2026-102271 was first published on September 28, 2026, with the most recent update on October 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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 (6th 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.

Book a Demo →Browse All CVEs