Skip to main content
CVE-2026-102269VulnerabilityPublished Updated

Prior to 2.14.0, PyJWT signature segment is affected because signature segment decoding accepts characters outside the

Affects pyjwtSource GCVE Database

0
Compare
Authoritative record:CVE-2026-102269· Medium 4.8

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

CVSS 3.1 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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).

Affected software

ProductAffectedFixed in
Ubuntu 26.10pyjwtpkg:deb/ubuntu/pyjwt?arch=source&distro=stonkingOther threatsAffected
  • 2.10.1-4ubuntu1 – 2.13.0-1ubuntu1.1
5 affected builds
Fixed in–
Ubuntu 26.04 LTSpyjwtpkg:deb/ubuntu/pyjwt?arch=source&distro=resoluteOther threatsAffected
  • <2.10.1-4ubuntu1.4
Fixed in
  • 2.10.1-4ubuntu1.4
Ubuntu 24.04 LTSpyjwtpkg:deb/ubuntu/pyjwt?arch=source&distro=nobleOther threatsAffected
  • <2.7.0-1ubuntu0.5
Fixed in
  • 2.7.0-1ubuntu0.5
Ubuntu 22.04 LTSpyjwtpkg:deb/ubuntu/pyjwt?arch=source&distro=jammyOther threatsAffected
  • <2.3.0-1ubuntu0.7
Fixed in
  • 2.3.0-1ubuntu0.7
Ubuntu Pro 20.04 LTSpyjwtpkg:deb/ubuntu/pyjwt?arch=source&distro=esm-infra/focalOther threatsAffected
  • 1.7.0-2 – 1.7.1-2ubuntu2.1+esm4
9 affected builds
Fixed in–
Ubuntu Pro 18.04 LTSpyjwtpkg:deb/ubuntu/pyjwt?arch=source&distro=esm-infra/bionicOther threatsAffected
  • 1.4.2-1.1 – 1.5.3+ds1-1ubuntu0.1+esm4
7 affected builds
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

Community reviews

Loading reviews…