Bug 2542701 (CVE-2026-102275) - CVE-2026-102275 pyjwt: PyJWT: Token verification bypass via mismatched OKP key components
Summary: CVE-2026-102275 pyjwt: PyJWT: Token verification bypass via mismatched OKP ke...
Keywords:
Status: NEW
Alias: CVE-2026-102275
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-28 21:02 UTC by OSIDB Bzimport
Modified: 2026-09-28 21:07 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-28 21:02:30 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.