Patch Forecast
Yellow warning
Plan into this sprint.

CVE-2026-103001 · GHSA-gvp8-978c-rx2q

PyJWT.decode() reintroduces options-dict mutation, enabling silent claim-verification bypass on dict reuse

Risk score
52/100
CVSS
6.5 v3.1
Exploit chance (30 days)
0.2%
Published
30 Sep 2026

Open in the live forecast Today's forecast

What to know

What it is
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 veri…
Affected
PyJWT (pip) >= 2.11.0, <= 2.13.0
Fix
No patched version listed yet: check the advisory for mitigations.
Exploitation
Public proof of concept

Story map

Story map: PyJWTTHE FLAWSTHE FIXCVE-2026-103001PyJWT.decode() reintroducesoptions-dict mutation, enablingsilent claim-verification…CVSS 6.5 · EPSS 0%CVE-2026-102268Asymmetric-PEM detectionbypass:whitespace/line-ending-mutat…CVSS 9.1 · EPSS 0%CVE-2026-102266PyJWK accepts empty HMACkeys, bypassing PyJWT'sempty-key validationCVSS 9.1 · EPSS 0%CVE-2026-101917PyJWT: PyJWKClient stillamplifies unauthenticatedJWKS fetches on unknown kid…CVSS 7.5 · EPSS 0%Upgrade PyJWT2.14.0or later on your release lineWho is exposedPyJWT (pip) <= 2.13.0AMBER · PATCH THIS WEEKPyJWTPyJWT is a Pythonimplementation of JSON WebToken standards. Prior to 2.14.0,is_pem_format in jwt/utils.pyis affected becauseis_pem_format does notrecognize every PEM…Where it standsPublic proof of conceptCONNECTS TOSame productEarlier PyJWT warnings10 in the last 90 days →
Story map: the flaws, the fix, how it unfolded and what it connects to. Boxes link to the record or article.

At a glance

PyJWT: Amber, patch this week. PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, is_pem_format in jwt/utils.py is affected because is_pem_format does not recognize every PEM representation accepted by the cryptography loader. This occurs when an application mixes HMAC and asymmetric algorithms and supplies a mutated pub…

The flaws

  • CVE-2026-103001: PyJWT.decode() reintroduces options-dict mutation, enabling silent claim-verification bypass on dict reuse (CVSS 6.5 · EPSS 0%)
  • CVE-2026-102268: Asymmetric-PEM detection bypass: whitespace/line-ending-mutated public keys skip the HS/asymmetric confusion guard (CVSS 9.1 · EPSS 0%)
  • CVE-2026-102266: PyJWK accepts empty HMAC keys, bypassing PyJWT's empty-key validation (CVSS 9.1 · EPSS 0%)
  • CVE-2026-101917: PyJWT: PyJWKClient still amplifies unauthenticated JWKS fetches on unknown kid values (incomplete fix of CVE-2026-48524) (CVSS 7.5 · EPSS 0%)

The fix

Upgrade PyJWT: 2.14.0 or later on your release line

Who is exposed: PyJWT (pip) <= 2.13.0

Where it stands

  • Public proof of concept

Connects to

Why it is Yellow

  • CVSS 6.5 medium
  • Public exploit or proof of concept referenced
  • On your watchlist: PyPI

Affected packages

PackageEcosystemVulnerableFixed in
PyJWTpip>= 2.11.0, <= 2.13.0No fix yet

References

Original description

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.

Last activity 30 Sep 2026. Patch Forecast updates every hour.