PyJWT is a Python implementation of JSON Web Token standards. From 2.1.0 until 2.15.0, PyJWT OKPAlgorithm.from_jwk in jwt/algorithms.py is affected because private-JWK import path does not compare the public key derived from d with x. This occurs when an OKP private JWK supplies non-corresponding x and d components. As a result, identity derived from x can differ from operations performed with d. Consequently, if an integration also accepts private key parameters from a proof header without rejecting them, an attacker may use a stolen sender-constrained token without the legitimate private key. This issue is fixed in version 2.15.0.
CVE-2026-102275
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (2nd 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).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.5
- EG Score
- 6.5MEDIUMmedium confidence
- EG Risk
- 45EG Risk 45/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 computedSeverity65% × 45%Exploitation40% × 40%Automatability0% × 15%CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.1%
- EPSS %ILE
- 2nd
- KEV
- Not listed
CISA SSVCTrack 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). 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
September 30, 2026
Advisory Details (3)
Auto-updated Sep 28, 20262.15.0
Patch available: jpadilla/pyjwt 2.15.0
https://github.com/jpadilla/pyjwt/releases/tag/2.15.0commit 3cd9ceec33ce (jpadilla/pyjwt)
Patch available: jpadilla/pyjwt 2.15.0 (contains commit 3cd9ceec33ce)
https://github.com/jpadilla/pyjwt/commit/3cd9ceec33ced359decbad75b413ad668ae6332cPyJWT accepts inconsistent OKP x/d JWKs, causing public/private key identity confusion · Advisory · jpadilla/pyjwt · GitHub
https://github.com/jpadilla/pyjwt/security/advisories/GHSA-x33g-cr3x-6449Vendor Advisories for CVE-2026-102275(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 16× in last 7d / 16× 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.
- 2026-10-03 15:05 UTCEG score recompute
- 2026-10-03 15:05 UTCVendor advisory
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-02 16:38 UTCEG score recompute
- 2026-10-02 16:38 UTCVendor advisory
- 2026-10-01 19:49 UTCEPSS rescore
- 2026-10-01 18:10 UTCVendor advisory
- 2026-09-30 19:44 UTCEG score recompute
- 2026-09-30 15:02 UTCEPSS rescore
- 2026-09-30 12:42 UTCEG score recompute
- 2026-09-29 15:20 UTCEPSS rescore
- 2026-09-29 14:18 UTCEG score recompute
- 2026-09-29 14:04 UTCEG score recompute
- 2026-09-28 21:18 UTCEG score recompute
- 2026-09-28 20:58 UTCEG score recompute
- 2026-09-28 20:57 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-102275?
When was CVE-2026-102275 disclosed?
Is CVE-2026-102275 actively exploited?
What is the CVSS score of CVE-2026-102275?
How do I remediate CVE-2026-102275?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-102275
Is Your Infrastructure Affected by CVE-2026-102275?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.