| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-9j54-fg26-wv3r | PyJWT: PyJWK accepts empty HMAC keys, bypassing PyJWT's empty-key validation |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 29 Sep 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 29 Sep 2026 13:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Mon, 28 Sep 2026 22:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Jpadilla
Jpadilla pyjwt |
|
| Vendors & Products |
Jpadilla
Jpadilla pyjwt |
Mon, 28 Sep 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | PyJWK accepts empty HMAC keys, bypassing PyJWT's empty-key validation | |
| Weaknesses | CWE-347 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-09-29T19:35:42.049Z
Reserved: 2026-09-28T20:11:16.658Z
Link: CVE-2026-102266
Updated: 2026-09-29T19:35:35.828Z
Status : Received
Published: 2026-09-28T21:17:14.257
Modified: 2026-09-29T20:17:12.053
Link: CVE-2026-102266
OpenCVE Enrichment
Updated: 2026-09-28T22:15:08Z
Github GHSA