CVE & CISA-KEV Catalog

CVE-2026-102275

MEDIUM
6.5
CVSS v3
NVD

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.

How to fix

Remediation Available
pyjwtDebian
Fixed in:2.15.0-1CVE-2026-102275

TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works

Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredNone
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityLow
IntegrityHigh
AvailabilityNone

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N/E:U

Exploit Intelligence

0.14%probability of exploitation in 30 days
3rdpercentile

Low risk: more likely to be exploited than 3% of all known CVEs.

References

Exploit1
Release Notes1

Related Vulnerabilities

Other CWE-345 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2023-38831High7.8100%KEV + RansomFix
CVE-2016-4553High8.680%-Fix
CVE-2016-4554High8.639%-Fix
CVE-2023-35719Medium6.825%--
CVE-2022-26871Critical9.819%KEV-
CVE-2014-4936High9.317%--

Common questions

How do I fix CVE-2026-102275?

Upgrade pyjwt on debian unstable to 2.15.0-1 or later.

Is CVE-2026-102275 being actively exploited?

Not that we know of. CVE-2026-102275 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.14% is the estimated probability that it will be exploited in the next 30 days. That is higher than 3% of all scored CVEs.

How severe is CVE-2026-102275?

CVE-2026-102275 has a CVSS v3 base score of 6.5, rated moderate. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

What does CVE-2026-102275 affect?

Published advisories record a fix for pyjwt (Debian). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.

Embed a live status badge for CVE-2026-102275
CVE-2026-102275 severity badge

Markdown

[![CVE-2026-102275](https://tridentstack.com/cve/badge/CVE-2026-102275.svg)](https://tridentstack.com/cve/CVE-2026-102275)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-102275"><img src="https://tridentstack.com/cve/badge/CVE-2026-102275.svg" alt="CVE-2026-102275"></a>

Check your Linux endpoints for this class of vulnerability

TridentStack Control continuously scans Linux endpoints for known vulnerabilities and deploys the fixes from the same console. 200 endpoints free forever, no credit card.

Patch your fleet freeStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-06.