CVE-2026-102275
PyJWT is a Python implementation of JSON Web Token standards. From …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/jpadilla/pyjwt/commit/3cd9ceec33ced359decbad75b413ad668ae6332c
- github.com/jpadilla/pyjwt/releases/tag/2.15.0
- github.com/jpadilla/pyjwt/security/advisories/GHSA-x33g-cr3x-6449
- nvd.nist.gov/vuln/detail/CVE-2026-102275
- github.com/advisories/GHSA-x33g-cr3x-6449
- nvd.nist.gov/vuln/detail/CVE-2026-102275
- cve.org/CVERecord?id=CVE-2026-102275
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.