CVE-2026-102266

Published: Set 28, 2026 Last Modified: Set 28, 2026
ExploitDB:
Other exploit source:
Google Dorks:
HIGH 7,4
Source: [email protected]
Attack Vector: network
Attack Complexity: high
Privileges Required: none
User Interaction: none
Scope: unchanged
Confidentiality: high
Integrity: high
Availability: none

Description

AI Translation Available

PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, HMACAlgorithm.from_jwk is affected because PyJWK verification path used the decoded key without applying prepare_key validation. This occurs when a trusted JWK Set contains an oct entry with an empty k value. As a result, an attacker signs an HMAC token with the same zero-length key accepted by PyJWT. Consequently, forged token can carry arbitrary authenticated claims. This issue is fixed in version 2.14.0.

347

Improper Verification of Cryptographic Signature

Draft
Abstraction: Base Structure: Simple
Common Consequences
Security Scopes Affected:
Access Control Integrity Confidentiality
Potential Impacts:
Gain Privileges Or Assume Identity Modify Application Data Execute Unauthorized Code Or Commands
Applicable Platforms
All platforms may be affected
View CWE Details
https://github.com/jpadilla/pyjwt/commit/f91ed44dd65baaf457…
https://github.com/jpadilla/pyjwt/commit/f91ed44dd65baaf457f4b3353ed35e98a75393…
https://github.com/jpadilla/pyjwt/releases/tag/2.14.0
https://github.com/jpadilla/pyjwt/releases/tag/2.14.0
https://github.com/jpadilla/pyjwt/security/advisories/GHSA-…
https://github.com/jpadilla/pyjwt/security/advisories/GHSA-9j54-fg26-wv3r