CVE-2026-102267 · GHSA-9v7f-9g4p-ffgj
PyJWT: PyJWKClient follows redirects when fetching JWKS
- Risk score
- 66/100
- CVSS
- 9.1 v3.1
- Exploit chance (30 days)
- 0.2%
- Published
- 28 Sep 2026
Open in the live forecast Today's forecast
What to know
- What it is
- PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT PyJWKClient is affected because redirect destinations are not revalidated against the JWKS trust boundary. This occurs when a configured trusted JWKS endpoint returns an attacker-influenced redirect. As a result, PyJWKClient follows t…
- Affected
- PyJWT (pip) <= 2.13.0
- Fix
- Upgrade PyJWT to 2.14.0 or later.
- Exploitation
- No known exploitation
Story map
At a glance
PyJWT: Amber, patch this week. PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, is_pem_format in jwt/utils.py is affected because is_pem_format does not recognize every PEM representation accepted by the cryptography loader. This occurs when an application mixes HMAC and asymmetric algorithms and supplies a mutated pub…
The flaws
- CVE-2026-102267: PyJWKClient follows redirects when fetching JWKS (CVSS 9.1 · EPSS 0%)
- CVE-2026-102268: Asymmetric-PEM detection bypass: whitespace/line-ending-mutated public keys skip the HS/asymmetric confusion guard (CVSS 9.1 · EPSS 0%)
- CVE-2026-102266: PyJWK accepts empty HMAC keys, bypassing PyJWT's empty-key validation (CVSS 9.1 · EPSS 0%)
- CVE-2026-101917: PyJWT: PyJWKClient still amplifies unauthenticated JWKS fetches on unknown kid values (incomplete fix of CVE-2026-48524) (CVSS 7.5 · EPSS 0%)
The fix
Upgrade PyJWT: 2.14.0 or later on your release line
Who is exposed: PyJWT (pip) <= 2.13.0
Where it stands
- Public proof of concept
Connects to
- Same weakness: Information disclosure (CWE-200). 197 other warnings in 30 days
- Same product: Earlier PyJWT warnings. 10 in the last 90 days
Why it is Amber
- CVSS 9.1 critical
- Remotely exploitable without logging in
- On your watchlist: PyPI
Affected packages
| Package | Ecosystem | Vulnerable | Fixed in |
|---|---|---|---|
| PyJWT | pip | <= 2.13.0 | 2.14.0 |
References
- https://github.com/advisories/GHSA-9v7f-9g4p-ffgj
- https://github.com/jpadilla/pyjwt/security/advisories/GHSA-9v7f-9g4p-ffgj
- https://nvd.nist.gov/vuln/detail/CVE-2026-102267
- https://github.com/jpadilla/pyjwt/commit/0a795b8e1f6ef08f634aa7086fc41cc6d5ce3e56
- https://github.com/jpadilla/pyjwt/releases/tag/2.14.0
- https://github.com/advisories/GHSA-9v7f-9g4p-ffgj
Original description
PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT PyJWKClient is affected because redirect destinations are not revalidated against the JWKS trust boundary. This occurs when a configured trusted JWKS endpoint returns an attacker-influenced redirect. As a result, PyJWKClient follows the redirect and consumes the redirected response as key material. Consequently, forwarded credentials may be disclosed or verification keys may be substituted. This issue is fixed in version 2.14.0.
Last activity 28 Sep 2026. Patch Forecast updates every hour.