Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
PyJWT versions before 2.14.0, including 2.13.0, have a flaw in PyJWKClient, which followed HTTP redirects when fetching a JWKS without validating the destination. An attacker who can influence the response from the configured JWKS endpoint could redirect the client to another host, potentially exposing caller-supplied request headers and poisoning the key material used to accept JWTs. Upgrade to PyJWT 2.14.0, which fixes the issue.
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.0016, the 5th 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-9v7f-9g4p-ffgj
- OSV: GHSA-9v7f-9g4p-ffgj
- github.com/jpadilla/pyjwt/security/advisories/GHSA-9v7f-9g4p-ffgj
- nvd.nist.gov/vuln/detail/CVE-2026-102267
- github.com/jpadilla/pyjwt/commit/0a795b8e1f6ef08f634aa7086fc41cc6d5ce3e56
- github.com/jpadilla/pyjwt
- github.com/jpadilla/pyjwt/releases/tag/2.14.0