PyJWT BOM Bypass

Answer in brief

CVE-2026-102272 records a High severity (CVSS 7.4) vulnerability in PyJWT BOM Bypass. The current sources do not mark it as known exploited. The current feed maps jpadilla/pyjwt (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 28, 2026Updated Sep 28, 2026Source checked Sep 29, 2026First seen by HOL Sep 28, 2026Material review Sep 28, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.4
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 7.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps jpadilla/pyjwt (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
jpadilla/pyjwtgeneric	>=2.13.0 <2.14.0	2.14.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for jpadilla/pyjwt.
Review the reported fix. Update jpadilla/pyjwt to 2.14.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 28, 2026

Sources and claim methodology

Upstream source description

PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, HMACAlgorithm.prepare_key in jwt/algorithms.py is affected because raw-JWK detector does not normalize accepted Unicode byte-order marks before checking for JSON. This occurs when a public JWK is prefixed with a UTF-8 BOM and used in a mixed-algorithm verification path. As a result, public JWK bypasses asymmetric-key detection and becomes the HMAC secret. Consequently, an attacker who knows the public key can forge authenticated tokens. This issue is fixed in version 2.14.0.

Quoted source text, attributed separately from HOL analysis.