Skip to main content
CVE-2026-102275VulnerabilityPublished Updated

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

Affects MicrosoftSource GCVE Database

0
Compare
Authoritative record:CVE-2026-102275· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.15.0 when convenient.

Data as of 16 Nov 2026, 08:34 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2.15.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade pyjwt to 2.15.0.

Affected software

ProductAffectedFixed in
jpadillapyjwtAffected
  • >=2.1.0 <2.15.0
Fixed in
  • 2.15.0
PyPIpyjwtpkg:pypi/pyjwtOther threatsAffected
  • >=2.1.0 <2.15.0
Fixed in
  • 2.15.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle

References

Community reviews

Loading reviews…