Prior to 2.14.0, PyJWT signature segment is affected because signature segment decoding accepts characters outside the
Affects pyjwtSource GCVE Database
Not known to be exploited · CVSS 4.8 Medium · fixed in 2.3.0-1ubuntu0.7 : update pyjwt when convenient.
Data as of 20 Nov 2026, 09:25 UTC
- Patch
- Available – fixed in 2.3.0-1ubuntu0.7, 2.7.0-1ubuntu0.5, 2.10.1-4ubuntu1.4
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation 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
Upgrade the Ubuntu pyjwt to 2.3.0-1ubuntu0.7 (package) or 2.7.0-1ubuntu0.5 (package) or 2.10.1-4ubuntu1.4 (package).
Patches and advisories
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
A fix for this vulnerability is available and has been released in PyJWT version 2.14.0. Ubuntu users should update to the fixed package versions: 2.3.0-1ubuntu0.7 for 22.04 LTS, 2.7.0-1ubuntu0.5 for 24.04 LTS, and 2.10.1-4ubuntu1.4 for 26.04 LTS. Applying these updates will correct the signature decoding behavior and prevent bypass of token revocation checks. Standard system updates are recommended to apply these fixes.
Description
PyJWT versions prior to 2.14.0 have a vulnerability in signature segment decoding where non-Base64URL characters appended to a valid signature segment are accepted. This causes the base64url_decode function to produce identical signature bytes for different serialized segments, potentially allowing bypass of raw-token revocation checks. The issue is fixed in PyJWT version 2.14.0.
References
- ubuntu.com/security/CVE-2026-102269 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-102269 (opens in a new tab)
- github.com/jpadilla/pyjwt/security/advisories/GHSA-hxm8-2xgr-2p9m (opens in a new tab)
- github.com/jpadilla/pyjwt/commit/e6f48401001609a8f99e71fcaf355fb895d508a8 (opens in a new tab)
- github.com/jpadilla/pyjwt/releases/tag/2.14.0 (opens in a new tab)
- ubuntu.com/security/notices/USN-9177-1 (opens in a new tab)