Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
PyJWT (PyPI package pyjwt) versions before 2.14.0 are affected. When a jwt.decode allow-list mixes an HMAC algorithm with an asymmetric one, and the verification key is raw PEM text in a form that cryptography accepts but PyJWT's PEM detection misses, an attacker who holds the public key can forge HS256 tokens that verify. Upgrade to pyjwt 2.14.0, which contains the fix. Alternatively, use only asymmetric algorithms in the allow-list or verify with PyJWK objects.
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 |
|---|---|---|---|---|
| 9.1 | Critical | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0024, the 14th 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-ffc3-869f-jxw9
- OSV: GHSA-ffc3-869f-jxw9
- github.com/jpadilla/pyjwt/security/advisories/GHSA-ffc3-869f-jxw9
- nvd.nist.gov/vuln/detail/CVE-2026-102268
- github.com/jpadilla/pyjwt/commit/8b4e233a22206b34ec1186e912e75c0b2396ac07
- github.com/jpadilla/pyjwt
- github.com/jpadilla/pyjwt/releases/tag/2.14.0