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 accept a public RSA, EC, or OKP key wrapped in a JWKS object, array, or similar container as an HMAC secret. An attacker who knows the public key can forge HS256, HS384, or HS512 tokens only if the application allows both HMAC and asymmetric algorithms and passes the same raw public JWK JSON as both the key and the HMAC secret. Upgrade to PyJWT 2.14.0, which contains the fix.
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.0018, the 6th 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-w2cx-738m-mc7w
- OSV: GHSA-w2cx-738m-mc7w
- github.com/jpadilla/pyjwt/security/advisories/GHSA-w2cx-738m-mc7w
- nvd.nist.gov/vuln/detail/CVE-2026-102273
- github.com/jpadilla/pyjwt/commit/801cd128528c62d9b23fcd161d1a2e1c17982f95
- github.com/jpadilla/pyjwt
- github.com/jpadilla/pyjwt/releases/tag/2.14.0