What’s Vulnerable › Vulnerabilities

CVE-2026-102275: PyJWT accepts inconsistent OKP x/d JWKs, causing public/private key identity confusion

• Severity: high (CVSS 8.2 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.2% probability of exploitation in the next 30 days
• Public exploit or detection template: yes
• Published: 2026-09-28 · updated 2026-10-06
• Weakness: CWE-345

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

• jpadilla pyjwt: from 2.1.0 before 2.15.0 — fixed in 2.15.0

How to fix

Upgrade to a fixed version: jpadilla pyjwt 2.15.0. Check the vendor advisory for mitigations.

References

• https://github.com/jpadilla/pyjwt/commit/3cd9ceec33ced359decbad75b413ad668ae6332c
• https://github.com/jpadilla/pyjwt/releases/tag/2.15.0
• https://github.com/jpadilla/pyjwt/security/advisories/GHSA-x33g-cr3x-6449
• https://github.com/jpadilla/pyjwt/security/advisories/GHSA-x33g-cr3x-6449

Get alerted when CVE-2026-102275 or the next vulnerability affects your stack