medium6.5
CVE-2026-102275
PyJWT accepts inconsistent OKP x/d JWKs, causing public/private key identity confusion
Impact
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 packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| pip | PyJWT | >= 2.1.0, <= 2.14.0 | 2.15.0 |
Affected products
| Vendor | Product | Affected versions |
|---|---|---|
| Pyjwt Project | Pyjwt | from 2.1.0 before 2.15.0 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://github.com/advisories/GHSA-x33g-cr3x-6449
- https://github.com/jpadilla/pyjwt/security/advisories/GHSA-x33g-cr3x-6449
- https://nvd.nist.gov/vuln/detail/CVE-2026-102275
- https://github.com/jpadilla/pyjwt/commit/3cd9ceec33ced359decbad75b413ad668ae6332c
- https://github.com/jpadilla/pyjwt/releases/tag/2.15.0