<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 16 Nov 2026 20:47:53 +0000</lastBuildDate>
    <item>
      <title>BREW-fastmcp-CVE-2026-114616 — Authlib accepts an empty HMAC key, allowing JWS/JWT signature forgery (HS256/HS384/HS512)</title>
      <link>https://cve.radiocsirt.org/vuln/brew-fastmcp-cve-2026-114616</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: fastmcp&lt;/p&gt;
&lt;p&gt;Reporter: Cavan Loughran, Celvex Group Inc.&lt;/p&gt;
&lt;p&gt;Summary&lt;/p&gt;
&lt;p&gt;Authlib&amp;#39;s symmetric (oct) key handling accepts an empty key (empty bytes b&amp;#39;&amp;#39; / empty string &amp;#39;&amp;#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).&lt;/p&gt;
&lt;p&gt;This is DISTINCT from Authlib&amp;#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.&lt;/p&gt;
&lt;p&gt;Affected versions&lt;/p&gt;
&lt;p&gt;Authlib &amp;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.&lt;/p&gt;
&lt;p&gt;Root cause (exact code location, release tag v1.7.2)&lt;/p&gt;
&lt;p&gt;- authlib/jose/rfc7518/oct_key.py, class OctKey:
  - validate_raw_key is a type-only check: `retur…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: fastmcp&lt;/p&gt;
&lt;p&gt;Reporter: Cavan Loughran, Celvex Group Inc.&lt;/p&gt;
&lt;p&gt;Summary&lt;/p&gt;
&lt;p&gt;Authlib&amp;#39;s symmetric (oct) key handling accepts an empty key (empty bytes b&amp;#39;&amp;#39; / empty string &amp;#39;&amp;#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).&lt;/p&gt;
&lt;p&gt;This is DISTINCT from Authlib&amp;#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.&lt;/p&gt;
&lt;p&gt;Affected versions&lt;/p&gt;
&lt;p&gt;Authlib &amp;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.&lt;/p&gt;
&lt;p&gt;Root cause (exact code location, release tag v1.7.2)&lt;/p&gt;
&lt;p&gt;- authlib/jose/rfc7518/oct_key.py, class OctKey:
  - validate_raw_key is a type-only check: `retur…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-fastmcp-cve-2026-114616</guid>
    </item>
    <item>
      <title>CLEANSTART-2026-IK58625 — Authlib is a Python library which builds OAuth and OpenID Connect servers</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-ik58625</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: airflow-3&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the airflow-3 package. Authlib is a Python library which builds OAuth and OpenID Connect servers.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: airflow-3&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the airflow-3 package. Authlib is a Python library which builds OAuth and OpenID Connect servers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-ik58625</guid>
    </item>
    <item>
      <title>EUVD-2026-398546</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-398546</link>
      <description>EUVD-2026-398546</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-398546</guid>
    </item>
    <item>
      <title>fkie_cve-2026-114616</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-114616</link>
      <description>&lt;p&gt;Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to 1.9.1, Authlib&amp;#39;s OctKey.import_key() and HMAC signing and verification path accept zero-length key material. If an application&amp;#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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to 1.9.1, Authlib&amp;#39;s OctKey.import_key() and HMAC signing and verification path accept zero-length key material. If an application&amp;#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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-114616</guid>
    </item>
    <item>
      <title>GHSA-8m4g-j4wp-wgcg — Authlib accepts an empty HMAC key, allowing JWS/JWT signature forgery (HS256/HS384/HS512)</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8m4g-j4wp-wgcg</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: Authlib&lt;/p&gt;
&lt;p&gt;Reporter: Cavan Loughran, Celvex Group Inc.&lt;/p&gt;
&lt;p&gt;Summary&lt;/p&gt;
&lt;p&gt;Authlib&amp;#39;s symmetric (oct) key handling accepts an empty key (empty bytes b&amp;#39;&amp;#39; / empty string &amp;#39;&amp;#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).&lt;/p&gt;
&lt;p&gt;This is DISTINCT from Authlib&amp;#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.&lt;/p&gt;
&lt;p&gt;Affected versions&lt;/p&gt;
&lt;p&gt;Authlib &amp;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.&lt;/p&gt;
&lt;p&gt;Root cause (exact code location, release tag v1.7.2)&lt;/p&gt;
&lt;p&gt;- authlib/jose/rfc7518/oct_key.py, class OctKey:
  - validate_raw_key is a type-only check: `retur…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: Authlib&lt;/p&gt;
&lt;p&gt;Reporter: Cavan Loughran, Celvex Group Inc.&lt;/p&gt;
&lt;p&gt;Summary&lt;/p&gt;
&lt;p&gt;Authlib&amp;#39;s symmetric (oct) key handling accepts an empty key (empty bytes b&amp;#39;&amp;#39; / empty string &amp;#39;&amp;#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).&lt;/p&gt;
&lt;p&gt;This is DISTINCT from Authlib&amp;#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.&lt;/p&gt;
&lt;p&gt;Affected versions&lt;/p&gt;
&lt;p&gt;Authlib &amp;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.&lt;/p&gt;
&lt;p&gt;Root cause (exact code location, release tag v1.7.2)&lt;/p&gt;
&lt;p&gt;- authlib/jose/rfc7518/oct_key.py, class OctKey:
  - validate_raw_key is a type-only check: `retur…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8m4g-j4wp-wgcg</guid>
    </item>
    <item>
      <title>PYSEC-2026-4356</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-4356</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: authlib&lt;/p&gt;
&lt;p&gt;Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to 1.9.1, Authlib&amp;#39;s OctKey.import_key() and HMAC signing and verification path accept zero-length key material. If an application&amp;#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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: authlib&lt;/p&gt;
&lt;p&gt;Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to 1.9.1, Authlib&amp;#39;s OctKey.import_key() and HMAC signing and verification path accept zero-length key material. If an application&amp;#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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-4356</guid>
    </item>
    <item>
      <title>RHSA-2026:92666 — Red Hat Security Advisory: satellite/foreman-mcp-server-rhel9 container image available as a Technology Preview</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:92666</link>
      <description>&lt;p&gt;mcp: mcp: Denial of Service via session memory exhaustion in streamable HTTP servers anyio: AnyIO: TLS certificate spoofing via improper internationalized domain name encoding authlib: authlib: Signature verification bypass via deserialize_json urllib3: urllib3: Traffic interception via HTTPS proxy TLS configuration override urllib3: urllib3: Denial of Service via unbounded memory allocation in chunk parser pyjwt: pyjwt: Verification key substitution via unvalidated JWKS redirects pyjwt: PyJWT: Authentication bypass via improper public key validation pyjwt: pyjwt: Token forgery via improper Unicode byte-order mark handling pyjwt: pyjwt: Token forgery via acceptance of public JWK containers as HMAC secrets joserfc: joserfc: Signature verification bypass via empty signatures array mcp: mcp: Denial of Service via unbounded HTTP request body buffering dnspython: dnspython: Denial of Service via excessive DNS compression pointer traversal authlib: Authlib: Authentication bypass via improper asymmetric key validation authlib: authlib: Authentication bypass via zero-length HMAC key authlib: authlib: Authorization bypass via missing client token verification&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;mcp: mcp: Denial of Service via session memory exhaustion in streamable HTTP servers anyio: AnyIO: TLS certificate spoofing via improper internationalized domain name encoding authlib: authlib: Signature verification bypass via deserialize_json urllib3: urllib3: Traffic interception via HTTPS proxy TLS configuration override urllib3: urllib3: Denial of Service via unbounded memory allocation in chunk parser pyjwt: pyjwt: Verification key substitution via unvalidated JWKS redirects pyjwt: PyJWT: Authentication bypass via improper public key validation pyjwt: pyjwt: Token forgery via improper Unicode byte-order mark handling pyjwt: pyjwt: Token forgery via acceptance of public JWK containers as HMAC secrets joserfc: joserfc: Signature verification bypass via empty signatures array mcp: mcp: Denial of Service via unbounded HTTP request body buffering dnspython: dnspython: Denial of Service via excessive DNS compression pointer traversal authlib: Authlib: Authentication bypass via improper asymmetric key validation authlib: authlib: Authentication bypass via zero-length HMAC key authlib: authlib: Authorization bypass via missing client token verification&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:92666</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-114616</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-114616</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:22.04:LTS: python-authlib, Ubuntu:Pro:24.04:LTS: python-authlib, Ubuntu:26.10: python-authlib, Ubuntu:Pro:26.04:LTS: python-authlib&lt;/p&gt;
&lt;p&gt;Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to 1.9.1, Authlib&amp;#39;s OctKey.import_key() and HMAC signing and verification path accept zero-length key material. If an application&amp;#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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:22.04:LTS: python-authlib, Ubuntu:Pro:24.04:LTS: python-authlib, Ubuntu:26.10: python-authlib, Ubuntu:Pro:26.04:LTS: python-authlib&lt;/p&gt;
&lt;p&gt;Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to 1.9.1, Authlib&amp;#39;s OctKey.import_key() and HMAC signing and verification path accept zero-length key material. If an application&amp;#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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-114616</guid>
    </item>
  </channel>
</rss>
