pyjwt
Affected
- introduced
2.1.0, fixed2.15.0(ecosystem)
Fixed versions
2.15.0
Fix
- Fixed version
2.15.0pip install --upgrade pyjwt==2.15.0
Advisory
Also known as: CVE-2026-102275, GHSA-x33g-cr3x-6449
The record has no summary.
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.
High Basis: CVSS v3 score 8.2, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
2.1.0, fixed 2.15.0 (ecosystem)2.15.0
2.15.0pip install --upgrade pyjwt==2.15.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: PyPA Advisory Database · CC BY 4.0