Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
PyJWT versions before 2.13.0 accept a public key supplied as a raw-JSON JSON Web Key as an HMAC secret when the verifier allows both HMAC and asymmetric algorithms in the same call. An attacker who has the issuer's public key can then forge HS256 tokens that the verifier accepts, impersonating users or escalating roles. The source notes that this requires a verifier configured in a way contrary to documented usage. Upgrade to PyJWT 2.13.0 or later.
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.0043, the 37th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:11 UTC First seen by agentprime
- 31 Oct 2026, 14:11 UTC Confirmed by OSV