Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
PyJWT versions from 2.0.0a1 before 2.15.0 are affected. When a token is decoded with signature verification turned off, or passed to `PyJWKClient.get_signing_key_from_jwt`, an unauthenticated attacker can send a token whose payload is deeply nested JSON. This raises an uncaught `RecursionError` instead of a PyJWT error, so the calling request fails with an unhandled exception. Upgrade to PyJWT 2.15.0.
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.0041, the 35th percentile, on 5 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-42vr-xj54-vc7v
- OSV: GHSA-42vr-xj54-vc7v
- github.com/jpadilla/pyjwt/security/advisories/GHSA-42vr-xj54-vc7v
- nvd.nist.gov/vuln/detail/CVE-2026-101918
- github.com/jpadilla/pyjwt/commit/5fde08a6cf906aa7698de2d6391d88b73006b17b
- github.com/jpadilla/pyjwt
- github.com/jpadilla/pyjwt/releases/tag/2.15.0