Patch Forecast
Amber warning
Patch this week.

CVE-2026-102275 · GHSA-x33g-cr3x-6449

PyJWT accepts inconsistent OKP x/d JWKs, causing public/private key identity confusion

Risk score
65/100
CVSS
8.2 v3.1
Exploit chance (30 days)
0.1%
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. From 2.1.0 until 2.15.0, PyJWT OKPAlgorithm.from_jwk in jwt/algorithms.py is affected because private-JWK import path does not compare the public key derived from d with x. This occurs when an OKP private JWK supplies non-corresponding x and d components. A…
Affected
PyJWT (pip) >= 2.1.0, <= 2.14.0
Fix
Upgrade PyJWT to 2.15.0 or later.
Exploitation
Public proof of concept

Story map

Story map: PyJWTTHE FLAWSTHE FIXCVE-2026-102275PyJWT accepts inconsistentOKP x/d JWKs, causingpublic/private key identity…CVSS 8.2 · EPSS 0%CVE-2026-102268Asymmetric-PEM detectionbypass:whitespace/line-ending-mutat…CVSS 9.1 · EPSS 0%CVE-2026-102266PyJWK accepts empty HMACkeys, bypassing PyJWT'sempty-key validationCVSS 9.1 · EPSS 0%CVE-2026-101917PyJWT: PyJWKClient stillamplifies unauthenticatedJWKS fetches on unknown kid…CVSS 7.5 · EPSS 0%Upgrade PyJWT2.15.0 · 2.14.0or later on your release lineWho is exposedPyJWT (pip) <= 2.13.0AMBER · PATCH THIS WEEKPyJWTPyJWT is a Pythonimplementation of JSON WebToken standards. Prior to 2.14.0,is_pem_format in jwt/utils.pyis affected becauseis_pem_format does notrecognize every PEM…Where it standsPublic proof of conceptCONNECTS TOSame weaknessCWE-345 (CWE-345)45 other warnings in 30 days →Same productEarlier PyJWT warnings10 in the last 90 days →
Story map: the flaws, the fix, how it unfolded and what it connects to. Boxes link to the record or article.

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-102275: PyJWT accepts inconsistent OKP x/d JWKs, causing public/private key identity confusion (CVSS 8.2 · 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.15.0 · 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

Why it is Amber

  • CVSS 8.2 high
  • Public exploit or proof of concept referenced
  • Remotely exploitable without logging in
  • On your watchlist: PyPI

Affected packages

PackageEcosystemVulnerableFixed in
PyJWTpip>= 2.1.0, <= 2.14.02.15.0

References

Original description

PyJWT is a Python implementation of JSON Web Token standards. From 2.1.0 until 2.15.0, PyJWT OKPAlgorithm.from_jwk in jwt/algorithms.py is affected because private-JWK import path does not compare the public key derived from d with x. This occurs when an OKP private JWK supplies non-corresponding x and d components. As a result, identity derived from x can differ from operations performed with d. Consequently, if an integration also accepts private key parameters from a proof header without rejecting them, an attacker may use a stolen sender-constrained token without the legitimate private key. This issue is fixed in version 2.15.0.

Last activity 28 Sep 2026. Patch Forecast updates every hour.