| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-8wjv-2p76-3863 | PyJWT: Uncaught RecursionError in jwt.decode() on deeply nested token header |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Thu, 01 Oct 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 29 Sep 2026 13:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-248 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Mon, 28 Sep 2026 23:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Jpadilla
Jpadilla pyjwt |
|
| Vendors & Products |
Jpadilla
Jpadilla pyjwt |
Mon, 28 Sep 2026 21:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, PyJWS._load in jwt/api_jws.py is affected because parser catches ValueError but not RecursionError. This occurs when a deeply nested token header reaches json.loads. As a result, RecursionError escapes the documented PyJWT error hierarchy. Consequently, an unauthenticated malformed token can cause a request-level failure and HTTP 500. This issue is fixed in version 2.14.0. | |
| Title | PyJWT: Uncaught RecursionError in jwt.decode() on deeply nested token header | |
| Weaknesses | CWE-674 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-01T15:01:31.377Z
Reserved: 2026-09-28T20:11:16.658Z
Link: CVE-2026-102265
Updated: 2026-10-01T15:01:19.632Z
Status : Awaiting Analysis
Published: 2026-09-28T21:17:14.077
Modified: 2026-10-01T15:17:25.207
Link: CVE-2026-102265
OpenCVE Enrichment
Updated: 2026-09-30T04:45:19Z
Github GHSA