Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-102275: PyJWT is a Python implementation of JSON Web Token standards

34
This week
MEDIUM 6.5REMOTEUPGRADE

CVE-2026-102275 is a medium-severity flaw (CVSS 6.5) affecting pyjwt. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 priv

Why this priority

  • Public exploit reference
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score6.5 (Medium)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance0.2% (top 94%)
CISA exploited listNo
WeaknessCWE-345, CWE-348
Published2026-09-28
Last modified2026-10-06
Publisher (CNA): GitHub, Inc. · Vendor: pyjwt project

Share: LinkedIn · X · Reddit

Last updated 2026-10-06 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

pyjwt project pyjwt UPGRADE
Affected: >= 2.1.0 and < 2.15.0
Fixed in: 2.15.0
Safe to downgrade to: a release before 2.1.0
1. Check installed version
apt-cache policy pyjwt || rpm -q pyjwt || pyjwt --version
2. UPGRADE to 2.15.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade pyjwt
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade pyjwt
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.1.0 (Debian / Ubuntu)
apt-cache madison pyjwt sudo apt install pyjwt=<VERSION_BEFORE_2.1.0> sudo apt-mark hold pyjwt
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list pyjwt sudo dnf downgrade pyjwt-<VERSION_BEFORE_2.1.0> sudo dnf versionlock add pyjwt
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-102275?

pyjwt: upgrade to 2.15.0. Exact commands for each OS are on this page.

Is CVE-2026-102275 being exploited?

CVE-2026-102275 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-102275 affect?

CVE-2026-102275 affects pyjwt. Severity is medium (CVSS 6.5). 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

How urgent is CVE-2026-102275?

Priority 34/100. Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Python vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.