Improperly Implemented Security Check for Standard Affecting python-jwt package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.24% (15th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-PYTHONJWT-20557804
  • published7 Oct 2026
  • disclosed30 Sept 2026

Introduced: 30 Sep 2026

NewCVE-2026-103001  (opens in a new tab)
CWE-358  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:8 python-jwt.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-jwt package and not the python-jwt package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

PyJWT is a Python implementation of JSON Web Token standards. From 2.11.0 through 2.13.0, PyJWT's PyJWT._merge_options() method can modify a caller-supplied mutable options mapping when verify_signature is false. If an application reuses that same mapping for a later decode() or decode_complete() call and changes verify_signature to true, the mapping can retain false values for expiration, not-before, issued-at, audience, issuer, subject, and JWT ID checks. A signed token with invalid registered claims can then be accepted without disabling signature verification, but applications that create a fresh options mapping for each call are not affected.

CVSS Base Scores

version 3.1