Description
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 products
pyjwt_project: pyjwt
References4
- github.com/jpadilla/pyjwt/security/advisories/GHSA-x33g-cr3x-64… ExploitVendor Advisory
- github.com/jpadilla/pyjwt/security/advisories/GHSA-x33g-cr3x-64… ExploitVendor Advisory
- github.com/jpadilla/pyjwt/commit/3cd9ceec33ced359decbad75b413ad… Patch
- github.com/jpadilla/pyjwt/releases/tag/2.15.0 ProductRelease Notes
Metrics
- CVSS 3.1
-
8.2
HIGH
Score source: NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N - EPSS — exploit probability
- 0% percentile: 6 · as of 9 November 2026
- CWE
- CWE-345CWE-348
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.