How severe is CVE-2026-102275?

CVE-2026-102275 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity high, and availability none.

Is CVE-2026-102275 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (3rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-102275?

CVE-2026-102275 affects Pyjwt Project Pyjwt. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-102275?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2026-102275 published?

CVE-2026-102275 was published on 2026-09-28 and last updated on 2026-10-06.

CVE-2026-102275

CVE-2026-102275 is a medium-severity vulnerability in Pyjwt Project Pyjwt with a CVSS 3.x base score of 6.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-345.

Key facts

Severity: Medium (CVSS 3.x base score 6.5)
EPSS exploit prediction: 0% (3rd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-345
Affected product: Pyjwt Project Pyjwt
Published: 2026-09-28
Last modified: 2026-10-06

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.

Frequently asked questions

What is CVE-2026-102275?: 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.
How severe is CVE-2026-102275?: CVE-2026-102275 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity high, and availability none.
Is CVE-2026-102275 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (3rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-102275?: CVE-2026-102275 affects Pyjwt Project Pyjwt. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-102275?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2026-102275 published?: CVE-2026-102275 was published on 2026-09-28 and last updated on 2026-10-06.

References

Affected products (1)

cpe:2.3:a:pyjwt_project:pyjwt:*:*:*:*:*:*:*:*

More vulnerabilities in Pyjwt Project Pyjwt

CVE-2026-32597 — High (CVSS 7.5): PyJWT is a JSON Web Token implementation in Python. Prior to 2.12.0, PyJWT does not validate the crit (Critical) Header…
CVE-2017-11424 — High (CVSS 7.5): In PyJWT 1.5.0 and below the `invalid_strings` check in `HMACAlgorithm.prepare_key` does not account for all PEM…
CVE-2026-102273 — High (CVSS 7.4): PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, PyJWT HMACAlgorithm.prepare_key…
CVE-2026-102272 — High (CVSS 7.4): PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, HMACAlgorithm.prepare_key in…
CVE-2026-102271 — High (CVSS 7.4): PyJWT is a Python implementation of JSON Web Token standards. From 2.4.0 until 2.14.0, PyJWT HMACAlgorithm.prepare_key…
CVE-2026-48526 — High (CVSS 7.4): PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, when the verifier is decoding JSON Web Tokens,…

All CVEs affecting Pyjwt Project Pyjwt →

Other CWE-345 (Insufficient Verification of Data Authenticity) vulnerabilities

CVE-2026-62874 — Critical (CVSS 10.0): Insufficient verification of data authenticity in Azure Billing allows an unauthorized attacker to elevate privileges…
CVE-2026-35051 — Critical (CVSS 10.0): Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2, there is an…
CVE-2014-8165 — Critical (CVSS 10.0): scripts/amsvis/powerpcAMS/amsnet.py in powerpc-utils-python uses the pickle Python module unsafely, which allows remote…
CVE-2026-50195 — Critical (CVSS 9.9): containerd is an open-source container runtime. Versions prior to 2.3.2, 2.2.5 and 2.1.9 contain a vulnerability in the…
CVE-2022-36130 — Critical (CVSS 9.9): HashiCorp Boundary up to 0.10.1 did not properly perform data integrity checks to ensure the resources were associated…
CVE-2026-104056 — Critical (CVSS 9.8): Authlib version 1.7.2 and below contains a vulnerability where discovery JSON metadata is cached without validation or…

Browse all CWE-345 (Insufficient Verification of Data Authenticity) vulnerabilities →