CVE-2026-102275

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.

Severity
MEDIUM
CVSS v3
6.5
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N · source cna
Exploit chance (EPSS)
0.167%
chance of exploitation in the next 30 days
higher than 6% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
Yes
Exploit references (NVD and CNA): 1
Metasploit modules: 0
Nuclei templates: 0

Weakness

CISA SSVC decision points

Exploitationpoc
Automatableno
Technical impactpartial
Scored2026-09-29

Timeline

  1. 2026-09-28Published by the CNA20:46 UTC
  2. 2026-09-29CISA SSVC decision recorded1 day after publication
  3. 2026-10-05GitHub advisory published (GHSA-x33g-cr3x-6449)7 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-x33g-cr3x-6449, affected packages:

PackageVulnerable versionsFixed in
PyPI pyjwtfrom 2.1.0 before 2.15.02.15.0

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
pyjwt_project pyjwtfrom 2.1.0 before 2.15.0fixed in 2.15.02.15.0

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources