CVE-2026-102270

Description

PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT is_pem_format is affected because lazy PEM regular expression backtracks extensively. This occurs when a certificate-like input contains repeated BEGIN markers without a matching END marker. As a result, is_pem_format performs unbounded backtracking while searching for a PEM end marker. Consequently, an attacker can cause intensive CPU consumption. This issue is fixed in version 2.14.0.

Severity
MEDIUM
CVSS v3
4.4
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H · source cna
Exploit chance (EPSS)
0.246%
chance of exploitation in the next 30 days
higher than 15.9% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
Yes
Exploit references (NVD and CNA): 1
Metasploit modules: 0
Nuclei templates: 0

Weakness

CISA SSVC decision points

Exploitationpoc
Automatableno
Technical impactpartial
Scored2026-09-29

Timeline

  1. 2026-09-28Published by the CNA20:29 UTC
  2. 2026-09-29CISA SSVC decision recorded1 day after publication
  3. 2026-09-30GitHub advisory published (GHSA-jwrc-g2q2-pq5p)2 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-jwrc-g2q2-pq5p, affected packages:

PackageVulnerable versionsFixed in
PyPI pyjwtbefore 2.14.02.14.0

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
pyjwt_project pyjwtbefore 2.14.0fixed in 2.14.02.14.0

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources