PoC Monitor
← All CVEs
CVE-2026-102275published 28 Sep 2026 20:46 UTCData: JSON · API

PyJWT

PyJWT accepts inconsistent OKP x/d JWKs, causing public/private key identity confusion

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.2high · scored by NVD · CWE-345
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

jpadilla pyjwt
  • >= 2.1.0, < 2.15.0

Fixed in 2.15.0

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published28 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.