| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-jwrc-g2q2-pq5p | PyJWT: ReDoS vulnerability when calling the `is_pem_format` function. |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 29 Sep 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 29 Sep 2026 13:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Mon, 28 Sep 2026 22:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Jpadilla
Jpadilla pyjwt |
|
| Vendors & Products |
Jpadilla
Jpadilla pyjwt |
Mon, 28 Sep 2026 20:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | PyJWT: ReDoS vulnerability when calling the `is_pem_format` function. | |
| Weaknesses | CWE-1333 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-09-29T19:36:54.944Z
Reserved: 2026-09-28T20:11:16.658Z
Link: CVE-2026-102270
Updated: 2026-09-29T19:36:47.026Z
Status : Awaiting Analysis
Published: 2026-09-28T21:17:14.943
Modified: 2026-09-30T19:38:27.293
Link: CVE-2026-102270
OpenCVE Enrichment
Updated: 2026-09-28T22:15:08Z
Github GHSA