https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 02 Nov 2026 13:22:05 +0000 https://db.gcve.eu/vuln/cve-2026-114616 <p><strong>Affected:</strong> authlib</p> <p>Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to 1.9.1, Authlib&#39;s OctKey.import_key() and HMAC signing and verification path accept zero-length key material. If an application&#39;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.</p> <p><strong>Affected:</strong> authlib</p> <p>Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to 1.9.1, Authlib&#39;s OctKey.import_key() and HMAC signing and verification path accept zero-length key material. If an application&#39;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.</p> https://db.gcve.eu/vuln/cve-2026-114616 https://db.gcve.eu/vuln/ghsa-8m4g-j4wp-wgcg <p><strong>Affected:</strong> PyPI: Authlib</p> <p>Reporter: Cavan Loughran, Celvex Group Inc.</p> <p>Summary</p> <p>Authlib&#39;s symmetric (oct) key handling accepts an empty key (empty bytes b&#39;&#39; / empty string &#39;&#39;) as a valid HMAC signing and verification key. An empty HMAC key produces a deterministic digest that any party can reproduce, so an attacker who knows (or can cause) the application to verify a token with an empty key can forge arbitrary tokens that pass HS256/HS384/HS512 signature verification. This is the Authlib member of the cross-language empty-HMAC-key family already assigned CVE-2026-44351 (fast-jwt, npm) and CVE-2026-45363 (ruby-jwt, RubyGems).</p> <p>This is DISTINCT from Authlib&#39;s existing recent JWT-verification advisories. It is not closed by CVE-2026-27962 / GHSA-wvwj-cvrp-7pv5 (JWS JWK header injection, the key=None case), nor by CVE-2026-28802 / GHSA-7wc2-qxgw-g8gg (alg:none blank-signature bypass), nor by GHSA-5357-c2jx-v7qh (algorithm confusion with asymmetric public keys). Those address header-driven key injection, the none algorithm, and asymmetric-vs-symmetric confusion respectively; none of them rejects a zero-length oct key.</p> <p>Affected versions</p> <p>Authlib &lt;= 1.7.2 (latest release 1.7.2, 2026-05-06). Confirmed present at the v1.7.2 release tag and on the current main HEAD. The affected code is in authlib/jose/rfc7518/oct_key.py and authlib/jose/rfc7518/jws_algs.py.</p> <p>Root cause (exact code location, release tag v1.7.2)</p> <p>- authlib/jose/rfc7518/oct_key.py, class OctKey: - validate_raw_key is a type-only check: `retur…</p> <p><strong>Affected:</strong> PyPI: Authlib</p> <p>Reporter: Cavan Loughran, Celvex Group Inc.</p> <p>Summary</p> <p>Authlib&#39;s symmetric (oct) key handling accepts an empty key (empty bytes b&#39;&#39; / empty string &#39;&#39;) as a valid HMAC signing and verification key. An empty HMAC key produces a deterministic digest that any party can reproduce, so an attacker who knows (or can cause) the application to verify a token with an empty key can forge arbitrary tokens that pass HS256/HS384/HS512 signature verification. This is the Authlib member of the cross-language empty-HMAC-key family already assigned CVE-2026-44351 (fast-jwt, npm) and CVE-2026-45363 (ruby-jwt, RubyGems).</p> <p>This is DISTINCT from Authlib&#39;s existing recent JWT-verification advisories. It is not closed by CVE-2026-27962 / GHSA-wvwj-cvrp-7pv5 (JWS JWK header injection, the key=None case), nor by CVE-2026-28802 / GHSA-7wc2-qxgw-g8gg (alg:none blank-signature bypass), nor by GHSA-5357-c2jx-v7qh (algorithm confusion with asymmetric public keys). Those address header-driven key injection, the none algorithm, and asymmetric-vs-symmetric confusion respectively; none of them rejects a zero-length oct key.</p> <p>Affected versions</p> <p>Authlib &lt;= 1.7.2 (latest release 1.7.2, 2026-05-06). Confirmed present at the v1.7.2 release tag and on the current main HEAD. The affected code is in authlib/jose/rfc7518/oct_key.py and authlib/jose/rfc7518/jws_algs.py.</p> <p>Root cause (exact code location, release tag v1.7.2)</p> <p>- authlib/jose/rfc7518/oct_key.py, class OctKey: - validate_raw_key is a type-only check: `retur…</p> https://db.gcve.eu/vuln/ghsa-8m4g-j4wp-wgcg https://db.gcve.eu/vuln/pysec-2026-4356 <p><strong>Affected:</strong> PyPI: authlib</p> <p>Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to 1.9.1, Authlib&#39;s OctKey.import_key() and HMAC signing and verification path accept zero-length key material. If an application&#39;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.</p> <p><strong>Affected:</strong> PyPI: authlib</p> <p>Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to 1.9.1, Authlib&#39;s OctKey.import_key() and HMAC signing and verification path accept zero-length key material. If an application&#39;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.</p> https://db.gcve.eu/vuln/pysec-2026-4356