<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-16T18:10:10.855641+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/brew-fastmcp-cve-2026-114615</id>
    <title>BREW-fastmcp-CVE-2026-114615 — Authlib incomplete algorithm-confusion fix permits HMAC forgery with prefixed public keys</title>
    <updated>2026-11-16T18:10:11.096184+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: fastmcp</p>
<p>## Summary</p>
<p>`OctKey.import_key()` carries the only guard that stops an asymmetric public key from being used as an
HMAC secret in `authlib.jose`. That guard is `raw_key.startswith(POSSIBLE_UNSAFE_KEYS)` — anchored at
byte 0 — while the loader that consumes the identical bytes on the asymmetric path
(`cryptography.hazmat.primitives.serialization.load_pem_public_key` / `load_pem_x509_certificate`)
skips anything before the `-----BEGIN` line. A PEM public key or X.509 certificate carrying **one
leading byte** — a newline, a space, four spaces of indentation, a UTF-8 BOM, or a comment line — is
therefore not recognised, falls through, and becomes the HMAC secret. An attacker holding only the
issuer's public key then mints an `HS256` token with arbitrary claims that `jwt.decode()` accepts as
authentic.</p>
<p>This is an incomplete fix of **CVE-2024-37568 / GHSA-5357-c2jx-v7qh**. That advisory's fix is exactly
this guard (`git log -S 'POSSIBLE_UNSAFE_KEYS' -- authlib/jose/rfc7518/oct_key.py` returns a single
commit, `3bea812` "fix: prevent OctKey to import ssh/rsa/pem keys", referencing issue #654), and the
original attack works again unchanged whenever the stored PEM does not start at offset 0.</p>
<p>Reproduced end-to-end on **1.8.0**, the newest release (published 2026-08-30), and on `origin/main`
(`c529a61`), with `cryptography` 50.0.2.</p>
<p>## Preconditions</p>
<p>Both are deployment properties; neither is attacker-controlled at request time, and the attacker needs
no secret and no user interactio…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-fastmcp-cve-2026-114615"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cleanstart-2026-lu42138</id>
    <title>CLEANSTART-2026-LU42138 — Authlib is a Python library which builds OAuth and OpenID Connect servers</title>
    <updated>2026-11-16T18:10:11.096313+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> CleanStart: airflow-3</p>
<p>Security vulnerability affects the airflow-3 package. Authlib is a Python library which builds OAuth and OpenID Connect servers.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2026-lu42138"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-394927</id>
    <title>EUVD-2026-394927</title>
    <updated>2026-11-16T18:10:11.096337+00:00</updated>
    <content>EUVD-2026-394927</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-394927"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-114615</id>
    <title>fkie_cve-2026-114615</title>
    <updated>2026-11-16T18:10:11.096350+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Authlib is a Python library which builds OAuth and OpenID Connect servers. From 1.3.1 until 1.9.0, OctKey.import_key() checks asymmetric-key markers only at byte zero while Authlib's PEM loaders accept leading whitespace, comments, or a byte-order mark. In deployments that use the documented mixed algorithm registry and already configure verification with PEM or certificate bytes containing such a prefix, an unauthenticated attacker who knows those same public-key bytes can use them as an HMAC secret and forge HS256 tokens with arbitrary identity or authorization claims. This is a bypass of the remediation for CVE-2024-37568. The module-level jwt object reaches OctKey.import_key() in authlib/jose/rfc7518/oct_key.py, where POSSIBLE_UNSAFE_KEYS fails to identify prefixed asymmetric key material. This issue is fixed in version 1.9.0.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-114615"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-7vr2-2fgp-9w7p</id>
    <title>GHSA-7vr2-2fgp-9w7p — Authlib incomplete algorithm-confusion fix permits HMAC forgery with prefixed public keys</title>
    <updated>2026-11-16T18:10:11.096377+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: authlib</p>
<p>## Summary</p>
<p>`OctKey.import_key()` carries the only guard that stops an asymmetric public key from being used as an
HMAC secret in `authlib.jose`. That guard is `raw_key.startswith(POSSIBLE_UNSAFE_KEYS)` — anchored at
byte 0 — while the loader that consumes the identical bytes on the asymmetric path
(`cryptography.hazmat.primitives.serialization.load_pem_public_key` / `load_pem_x509_certificate`)
skips anything before the `-----BEGIN` line. A PEM public key or X.509 certificate carrying **one
leading byte** — a newline, a space, four spaces of indentation, a UTF-8 BOM, or a comment line — is
therefore not recognised, falls through, and becomes the HMAC secret. An attacker holding only the
issuer's public key then mints an `HS256` token with arbitrary claims that `jwt.decode()` accepts as
authentic.</p>
<p>This is an incomplete fix of **CVE-2024-37568 / GHSA-5357-c2jx-v7qh**. That advisory's fix is exactly
this guard (`git log -S 'POSSIBLE_UNSAFE_KEYS' -- authlib/jose/rfc7518/oct_key.py` returns a single
commit, `3bea812` "fix: prevent OctKey to import ssh/rsa/pem keys", referencing issue #654), and the
original attack works again unchanged whenever the stored PEM does not start at offset 0.</p>
<p>Reproduced end-to-end on **1.8.0**, the newest release (published 2026-08-30), and on `origin/main`
(`c529a61`), with `cryptography` 50.0.2.</p>
<p>## Preconditions</p>
<p>Both are deployment properties; neither is attacker-controlled at request time, and the attacker needs
no secret and no user interactio…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-7vr2-2fgp-9w7p"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2026-4355</id>
    <title>PYSEC-2026-4355</title>
    <updated>2026-11-16T18:10:11.096456+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: authlib</p>
<p>Authlib is a Python library which builds OAuth and OpenID Connect servers. From 1.3.1 until 1.9.0, OctKey.import_key() checks asymmetric-key markers only at byte zero while Authlib's PEM loaders accept leading whitespace, comments, or a byte-order mark. In deployments that use the documented mixed algorithm registry and already configure verification with PEM or certificate bytes containing such a prefix, an unauthenticated attacker who knows those same public-key bytes can use them as an HMAC secret and forge HS256 tokens with arbitrary identity or authorization claims. This is a bypass of the remediation for CVE-2024-37568. The module-level jwt object reaches OctKey.import_key() in authlib/jose/rfc7518/oct_key.py, where POSSIBLE_UNSAFE_KEYS fails to identify prefixed asymmetric key material. This issue is fixed in version 1.9.0.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2026-4355"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2026:92666</id>
    <title>RHSA-2026:92666 — Red Hat Security Advisory: satellite/foreman-mcp-server-rhel9 container image available as a Technology Preview</title>
    <updated>2026-11-16T18:10:11.096487+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2026:92666"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-114615</id>
    <title>UBUNTU-CVE-2026-114615</title>
    <updated>2026-11-16T18:10:11.096530+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>Authlib is a Python library which builds OAuth and OpenID Connect servers. From 1.3.1 until 1.9.0, OctKey.import_key() checks asymmetric-key markers only at byte zero while Authlib's PEM loaders accept leading whitespace, comments, or a byte-order mark. In deployments that use the documented mixed algorithm registry and already configure verification with PEM or certificate bytes containing such a prefix, an unauthenticated attacker who knows those same public-key bytes can use them as an HMAC secret and forge HS256 tokens with arbitrary identity or authorization claims. This is a bypass of the remediation for CVE-2024-37568. The module-level jwt object reaches OctKey.import_key() in authlib/jose/rfc7518/oct_key.py, where POSSIBLE_UNSAFE_KEYS fails to identify prefixed asymmetric key material. This issue is fixed in version 1.9.0.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-114615"/>
  </entry>
</feed>
