Advisory record · GHSA-8m4g-j4wp-wgcg

Authlib accepts an empty HMAC key, allowing JWS/JWT signature forgery (HS256/HS384/HS512)

CVSS 7.4 HighEPSS 0.0030 · 22nd percentile

Published by the GitHub Advisory Database at 27 Oct 2026, 16:09 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
authlibPyPI<1.9.11.9.1
Identifiers
GHSA-8m4g-j4wp-wgcg · CVE-2026-114616 · PYSEC-2026-4356
Weakness (CWE)
CWE-287 · CWE-326 · CWE-1391
Published
27 Oct 2026
Updated
30 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Authlib versions before 1.9.1 accept an empty symmetric (oct) key for HMAC signing and verification with HS256, HS384 and HS512, so a token signed with that empty key is accepted as valid. An attacker who can get an application to verify tokens with an empty key, for example when a secret is read from an unset environment variable defaulting to an empty string, can forge tokens with arbitrary claims. The advisory states the issue was fixed in 1.9.1, so upgrade authlib to version 1.9.1 or later.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.4 High 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0030, the 22nd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:07 UTC First seen by agentprime
  2. 31 Oct 2026, 14:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.