CYBER CODE RED

Get real-time updates on Telegram

P4

CVE-2026-102275: pyjwt from 2.1.0 (inclusive), before 2.15.0 (exclusive), >= 2.1.0, < 2.15.0

CVE-2026-102275 affects azl3 python-jwt 2.13.0-1 on Azure Linux 3.0. CVSS 3.1 base score 8.2 (HIGH, NVD). EPSS 0.00143 (percentile 0.03121), scored 12-Oct-2026. Fixed version: 2.15.0-1. Affected range: >= 2.1.0, <= 2.14.0. Fixed version: 2.15.0. Fixed version: 15.0.0_git20260812-r12. Fixed version: 14.0.0_git20260916-r7. Fixed version: 2.91.0-r0. Fixed version: 2.15.0-r0. Fixed version: 2.15.0-r0. Fixed version: 2.15.0-r0. Fixed version: 2.15.0-r0. Fixed version: 2.15.0-r0. Fixed version: 0.30.0-r0. Fixed version: 1.179.0-r0. Fixed version: 1.7.0.1-r2. Fixed version: 0.21.0-r4.

Affected technology

pyjwt · from 2.1.0 (inclusive), before 2.15.0 (exclusive)
pyjwt project

pyjwt · >= 2.1.0, < 2.15.0
jpadilla

Component: Not specified by the source

Attack conditions (Vendor/CNA, CVSS 3.1): Network (remote) · No privileges required · No user interaction required

Attack conditions (NVD, CVSS 3.1): Network (remote) · No privileges required · No user interaction required

What an attacker can do

The source says 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. Vendor/CNA’s CVSS 3.1 assessment (base score 6.5/10) rates confidentiality impact as low; integrity impact as high; availability impact as none. NVD’s CVSS 3.1 assessment (base score 8.2/10) rates confidentiality impact as low; integrity impact as high; availability impact as none.

Published

CWE
CWE-345, CWE-348
Product
azl3 python-jwt 2.13.0-1 on Azure Linux 3.0
CCR priority
32.8 /100 (P4)
CVSS 3.1
8.2 /10 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N · NVD
EPSS
0.00167 · percentile 0.06013 · 2026-11-18
KEV
no

Provenance

Stable permalink: https://cybercodered.org/item/cve-cve-2026-102275.html