Vulnerability in Jpadilla Pyjwt
CVE-2026-102275
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
- Jpadilla Pyjwt — versions >= 2.1.0, < 2.15.0
Weakness classification (CWE)
References
Frequently asked questions
- What is CVE-2026-102275?
- CVE-2026-102275 is a medium-severity vulnerability in Jpadilla Pyjwt, classified under Insufficient Verification of Data Authenticity. CVSS score: 6.5/10. Published 2026-09-28.
- How severe is CVE-2026-102275?
- Medium severity. CVSS v3 base score is 6.5 out of 10.