Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

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

Quick assessment

Affected
jpadilla pyjwt
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

PyJWT 是 JSON Web Token（JWT）标准的 Python 实现。在 2.1.0 到 2.15.0 版本中， 中的 方法存在安全漏洞，原因是其在导入私用 JWK（JSON Web Key）时，未验证由私钥参数 推导出的公钥是否与 坐标一致。当提供的 OKP 类型私用 JWK 中 和 分量不匹配时，就会触发此问题。结果是，从 派生的身份可能与使用 执行的实际操作不一致。因此，如果应用程序集成过程中接受来自证明头（proof header）的私钥参数且未加以拒绝，攻击者就可能利用被盗发的、受发送者约束（

CVSS 6.5 · Medium

Possible ATT&CK Techniques 1 AI

T1552.004 · Private Keys
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-102275

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
PyJWT accepts inconsistent OKP x/d JWKs, causing public/private key identity confusion
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
对数据真实性的验证不充分
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
jpadilla pyjwt >= 2.1.0, < 2.15.0 -

II. Public POCs for CVE-2026-102275

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-102275

请登录查看更多情报信息。

Other References for CVE-2026-102275 (3)

Same Patch Batch · jpadilla · 2026-09-28 · 13 CVEs total

CVE-2026-102268 9.1 CRITICAL PyJWT: Asymmetric-PEM detection bypass: whitespace/line-ending-mutated public keys skip th
CVE-2026-102266 7.4 HIGH PyJWK accepts empty HMAC keys, bypassing PyJWT's empty-key validation
CVE-2026-102267 7.4 HIGH PyJWT: PyJWKClient follows redirects when fetching JWKS
CVE-2026-102271 7.4 HIGH PyJWT: Public keys in DER form are accepted as HMAC secrets, bypassing the CVE-2022-29217
CVE-2026-102272 7.4 HIGH PyJWT BOM Bypass
CVE-2026-102273 7.4 HIGH PyJWT accepts public JWK containers as HMAC secrets
CVE-2026-102274 5.9 MEDIUM PyJWT: Malformed RSA JWK aborts parsing of an entire JWK Set
CVE-2026-101918 5.3 MEDIUM PyJWT: Unauthenticated RecursionError DoS in pre-verification payload parse (PyJWKClient.g
CVE-2026-101917 5.3 MEDIUM PyJWT: PyJWKClient still amplifies unauthenticated JWKS fetches on unknown kid values (inc
CVE-2026-102265 5.3 MEDIUM PyJWT: Uncaught RecursionError in jwt.decode() on deeply nested token header
CVE-2026-102269 4.8 MEDIUM PyJWT: Non-canonical signature segments enable raw-token revocation bypass
CVE-2026-102270 4.4 MEDIUM PyJWT: ReDoS vulnerability when calling the `is_pem_format` function.

IV. Related Vulnerabilities

Same product: pyjwt
Same vendor: jpadilla
Same weakness: CWE-345

V. Comments for CVE-2026-102275

No comments yet

Leave a comment