| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-8m4g-j4wp-wgcg | Authlib accepts an empty HMAC key, allowing JWS/JWT signature forgery (HS256/HS384/HS512) |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 10 Nov 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 29 Oct 2026 15:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:authlib:authlib:*:*:*:*:*:*:*:* |
Fri, 23 Oct 2026 12:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-347 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Fri, 23 Oct 2026 03:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Authlib
Authlib authlib |
|
| Vendors & Products |
Authlib
Authlib authlib |
Fri, 23 Oct 2026 00:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to 1.9.1, Authlib's OctKey.import_key() and HMAC signing and verification path accept zero-length key material. If an application's secret lookup can return an empty string or empty bytes, a remote attacker can compute the deterministic HS256, HS384, or HS512 signature for arbitrary token claims and have Authlib treat the token as authentic. This issue is fixed in version 1.9.1. | |
| Title | Authlib accepts an empty HMAC key, allowing JWS/JWT signature forgery (HS256/HS384/HS512) | |
| Weaknesses | CWE-1391 CWE-287 CWE-326 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-30T20:07:37.170Z
Reserved: 2026-10-21T20:34:25.600Z
Link: CVE-2026-114616
Updated: 2026-10-30T20:07:29.306Z
Status : Analyzed
Published: 2026-10-22T22:18:04.420
Modified: 2026-10-30T20:17:00.643
Link: CVE-2026-114616
OpenCVE Enrichment
Updated: 2026-10-23T13:30:07Z
Github GHSA