Is CVE-2026-102275 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-102275 being exploited in the wild.

How severe is CVE-2026-102275?

Medium severity, with a CVSS score of 6.5, published 28 September 2026.

Which products and versions are affected?

PyJWT 2.1.0 to 2.14.1; pyjwt (PyPI) >= 2.1.0, <= 2.14.0, ECOSYSTEM:introduced=2.1.0,fixed=2.15.0.

Is there a fix for CVE-2026-102275?

Yes. pyjwt (PyPI): upgrade to 2.15.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-102275 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-102275?

Check whether you run PyJWT or pyjwt (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-102275: PyJWT OKP algorithm key validation bypass

Q: Is there a fix for CVE-2026-102275?

Yes. pyjwt (PyPI): upgrade to 2.15.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-102275 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-102275?

Check whether you run PyJWT or pyjwt (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-102275 · Severity: medium · CVSS 6.5 · Published 2026-09-28

PyJWT is a Python library for creating and validating JSON Web Tokens (JWTs), commonly used for authentication in web applications. A vulnerability in versions 2.1.0 through 2.15.0 allows an attacker to use a stolen token without the legitimate private key by exploiting inconsistent key components in OKP (Octet string key pairs). An attacker could forge or manipulate sender-constrained tokens to impersonate another user or gain unauthorized access to protected resources.

Technologies: PyJWT, pyjwt (PyPI). Vendors: PyJWT, PyPI.

Quick answers

Is CVE-2026-102275 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-102275 being exploited in the wild.
How severe is CVE-2026-102275?: Medium severity, with a CVSS score of 6.5, published 28 September 2026.
Which products and versions are affected?: PyJWT 2.1.0 to 2.14.1; pyjwt (PyPI) >= 2.1.0, <= 2.14.0, ECOSYSTEM:introduced=2.1.0,fixed=2.15.0.
Is there a fix for CVE-2026-102275?: Yes. pyjwt (PyPI): upgrade to 2.15.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-102275 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-102275?: Check whether you run PyJWT or pyjwt (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

pyjwt (PyPI): upgrade to 2.15.0 or later
```
pip install "pyjwt>=2.15.0"
```

Technical details

The OKPAlgorithm.from_jwk() method in jwt/algorithms.py fails to validate that the public key derived from the private key component (d) matches the supplied public key component (x) in OKP private JWKs. An attacker can supply a JWK with mismatched x and d values, causing identity verification to use x while cryptographic operations use d, creating a key confusion vulnerability. This is fixed in version 2.15.0.

Affected products

PyJWT PyJWT 2.1.0 to 2.14.1

Identifiers

CVE-2026-102275
GHSA-x33g-cr3x-6449
PYSEC-2026-4183

Timeline

2026-09-28: disclosed
2026-09-23: patched: Version 2.15.0 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.