Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
PyJWT versions 2.13.0 up to but not including 2.14.0 are affected. When a JWT's header contains deeply nested JSON, jwt.decode() raises a RecursionError, which is not a PyJWTError, so applications that catch only PyJWT errors can fail with a server error. An unauthenticated attacker can trigger this with a single crafted unsigned token, causing repeated denial of service on token-validating endpoints. Upgrade to PyJWT 2.14.0, which translates this error into DecodeError.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.3 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0034, the 28th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:09 UTC First seen by agentprime
- 31 Oct 2026, 14:09 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-8wjv-2p76-3863
- OSV: GHSA-8wjv-2p76-3863
- github.com/jpadilla/pyjwt/security/advisories/GHSA-8wjv-2p76-3863
- nvd.nist.gov/vuln/detail/CVE-2026-102265
- github.com/jpadilla/pyjwt/commit/06573692ebcdec8831c3927513b3e87c31fbbb62
- github.com/jpadilla/pyjwt
- github.com/jpadilla/pyjwt/releases/tag/2.14.0