Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
PyJWT versions from 2.4.0 before 2.14.0 are vulnerable when an application verifies tokens with an RSA or EC public key that is also allowed for HS256 and that key is passed as DER bytes. An attacker who knows the public key can sign a forged token with it, which can allow login as any user. Upgrade to PyJWT 2.14.0. Applications using PyJWK or PyJWKClient are not affected.
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 |
|---|---|---|---|---|
| 7.4 | High | 3.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0022, the 11th percentile, on 7 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-p4g4-x82p-q773
- OSV: GHSA-p4g4-x82p-q773
- github.com/jpadilla/pyjwt/security/advisories/GHSA-p4g4-x82p-q773
- nvd.nist.gov/vuln/detail/CVE-2026-102271
- github.com/jpadilla/pyjwt/commit/2798504fa2663364573cf2d1043d8d7fef389499
- github.com/jpadilla/pyjwt
- github.com/jpadilla/pyjwt/releases/tag/2.14.0