Skip to main content
VulnerabilityPublished Updated

CVE-2026-103001: From 2.11.0 through 2.13.0, PyJWT's PyJWT._merge_options() method can modify a caller-supplied

Affects pyjwtSource GCVE Database

0
Compare
Authoritative record:CVE-2026-103001· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 20 Nov 2026, 09:25 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 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

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-2 – 2.10.1-4ubuntu1.4
9 affected builds
Fixed in–
Ubuntu 24.04 LTSpyjwtpkg:deb/ubuntu/pyjwt?arch=source&distro=nobleOther threatsAffected
  • 2.7.0-1 – 2.7.0-1ubuntu0.5
6 affected builds
Fixed in–
Ubuntu 22.04 LTSpyjwtpkg:deb/ubuntu/pyjwt?arch=source&distro=jammyOther threatsAffected
  • 1.7.1-2ubuntu2 – 2.3.0-1ubuntu0.7
10 affected builds
Fixed in–
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

As a mitigation, applications should avoid reusing the same mutable options mapping between decode calls, especially when toggling verify_signature. Creating a fresh options mapping for each decode or decode_complete call prevents this issue.

Description

PyJWT versions 2.11.0 through 2.13.0 contain a vulnerability in the _merge_options() method where a mutable options mapping supplied by the caller can be modified improperly when verify_signature is false. This can cause the mapping to retain false values for critical claim checks such as expiration and audience when reused with verify_signature set to true, potentially allowing acceptance of signed tokens with invalid claims. Applications that create a fresh options mapping for each decode call are not affected.

References

Community reviews

Loading reviews…