CVE-2026-102275
PyJWT accepts inconsistent OKP x/d JWKs, causing public/private key identity confusion
HIGH 8.2EPSS 0.1%
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.
- Affected
- jpadilla · pyjwt
- CVSS v3.1 NVD
- 8.2 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N - CVSS v3.1 GITHUB
- 6.5 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N - EPSS
- 0.14% chance of exploitation in the next 30 days, 3rd percentile
- Published
- 2026-09-28
- Updated
- 2026-09-29
Proof-of-concept exploits (1)
Security advisories
- jpadilla/pyjwt/security/advisories/GHSA-x33g-cr3x-6449
- jpadilla/pyjwt/commit/3cd9ceec33ced359decbad75b413ad668ae6332c