CVE-2026-102266
As a result, an attacker signs an HMAC token with the same zero-length key accepted by PyJWT.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.22%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, HMACAlgorithm.from_jwk is affected because PyJWK verification path used the decoded key without applying prepare_key validation. This occurs when a trusted JWK Set contains an oct entry with an empty k value. As a result, an attacker signs an HMAC token with the same zero-length key accepted by PyJWT. Consequently, forged token can carry arbitrary authenticated claims. This issue is fixed in version 2.14.0.
- CVSS 3.1
- 9.1 CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- EPSS
- 0.22% probability · 13th percentile
- Public exploits
- None in Exploit-DB
- CISA KEV
- Not listed
- Weakness
- CWE-347
- Affected
- pyjwt project/pyjwt
- Source
- security-advisories@github.com
EPSS moved from 0.2% on 29 September 2026 to 0.2% on 27 October 2026.
References
- https://github.com/jpadilla/pyjwt/commit/f91ed44dd65baaf457f4b3353ed35e98a753934cPatch
- https://github.com/jpadilla/pyjwt/releases/tag/2.14.0Product, Release Notes
- https://github.com/jpadilla/pyjwt/security/advisories/GHSA-9j54-fg26-wv3rExploit, Vendor Advisory
- https://github.com/jpadilla/pyjwt/security/advisories/GHSA-9j54-fg26-wv3rExploit, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.