CVE-2026-102265: Pyjwt · From 2.13.0 until 2.14.0, PyJWS._load in jwt/api_jws.py is affected because parser catches
Affects pyjwtSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium · fixed in 2.14.0 : update pyjwt when convenient.
Data as of 20 Nov 2026, 09:25 UTC
- Patch
- Available – fixed in 2.14.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 28 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10pyjwtpkg:deb/ubuntu/pyjwt?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSpyjwtpkg:deb/ubuntu/pyjwt?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSpyjwtpkg:deb/ubuntu/pyjwt?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSpyjwtpkg:deb/ubuntu/pyjwt?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu Pro 20.04 LTSpyjwtpkg:deb/ubuntu/pyjwt?arch=source&distro=esm-infra/focalOther threats | Affected
| Fixed in– |
Ubuntu Pro 18.04 LTSpyjwtpkg:deb/ubuntu/pyjwt?arch=source&distro=esm-infra/bionicOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade PyJWT to version 2.14.0 or later, where this issue is fixed. No other mitigations are indicated or required.
Description
PyJWT versions from 2.13.0 up to but not including 2.14.0 contain a vulnerability in the PyJWS._load function where a RecursionError is not properly caught during JSON parsing of deeply nested token headers. This causes the error to escape the PyJWT error handling, resulting in an unauthenticated malformed token triggering a request-level failure and HTTP 500 response. The issue is fixed in version 2.14.0.
References
- ubuntu.com/security/CVE-2026-102265 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-102265 (opens in a new tab)
- github.com/jpadilla/pyjwt/security/advisories/GHSA-8wjv-2p76-3863 (opens in a new tab)
- github.com/jpadilla/pyjwt/commit/06573692ebcdec8831c3927513b3e87c31fbbb62 (opens in a new tab)
- github.com/jpadilla/pyjwt/releases/tag/2.14.0 (opens in a new tab)