<?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>Fri, 02 Oct 2026 23:56:23 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-10494</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-10494</link>
      <description>bdu:2026-10494</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-10494</guid>
    </item>
    <item>
      <title>BIT-openbao-2026-46405 — OpenBao's Kerberos Auth Method Accumulates Unaccessible Tokens</title>
      <link>https://cve.radiocsirt.org/vuln/bit-openbao-2026-46405</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 version 2.5.4, in OpenBao&amp;#39;s Kerberos auth method on the `GET` handler, or when an `Authorization: Negotiate` header is supplied, the response is includes a `logical.Auth` object in addition to an error message. This results in tokens being created with only the default policy, default TTL, and no entity information, which are hidden by the returned error message. No access to these tokens by the caller occurs and the authentication token is not ever made accessible outside of `sys/raw`. This is fixed in OpenBao v2.5.4. As a workaround, users may set a rate limit quota to limit the creation of these paths. As the path is unauthenticated, it isn&amp;#39;t possible to deny access to it.&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 version 2.5.4, in OpenBao&amp;#39;s Kerberos auth method on the `GET` handler, or when an `Authorization: Negotiate` header is supplied, the response is includes a `logical.Auth` object in addition to an error message. This results in tokens being created with only the default policy, default TTL, and no entity information, which are hidden by the returned error message. No access to these tokens by the caller occurs and the authentication token is not ever made accessible outside of `sys/raw`. This is fixed in OpenBao v2.5.4. As a workaround, users may set a rate limit quota to limit the creation of these paths. As the path is unauthenticated, it isn&amp;#39;t possible to deny access to it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-openbao-2026-46405</guid>
    </item>
    <item>
      <title>EUVD-2026-351987</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-351987</link>
      <description>EUVD-2026-351987</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-351987</guid>
    </item>
    <item>
      <title>fkie_cve-2026-46405</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-46405</link>
      <description>&lt;p&gt;OpenBao is an open source identity-based secrets management system. Prior to version 2.5.4, in OpenBao&amp;#39;s Kerberos auth method on the `GET` handler, or when an `Authorization: Negotiate` header is supplied, the response is includes a `logical.Auth` object in addition to an error message. This results in tokens being created with only the default policy, default TTL, and no entity information, which are hidden by the returned error message. No access to these tokens by the caller occurs and the authentication token is not ever made accessible outside of `sys/raw`. This is fixed in OpenBao v2.5.4. As a workaround, users may set a rate limit quota to limit the creation of these paths. As the path is unauthenticated, it isn&amp;#39;t possible to deny access to it.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenBao is an open source identity-based secrets management system. Prior to version 2.5.4, in OpenBao&amp;#39;s Kerberos auth method on the `GET` handler, or when an `Authorization: Negotiate` header is supplied, the response is includes a `logical.Auth` object in addition to an error message. This results in tokens being created with only the default policy, default TTL, and no entity information, which are hidden by the returned error message. No access to these tokens by the caller occurs and the authentication token is not ever made accessible outside of `sys/raw`. This is fixed in OpenBao v2.5.4. As a workaround, users may set a rate limit quota to limit the creation of these paths. As the path is unauthenticated, it isn&amp;#39;t possible to deny access to it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-46405</guid>
    </item>
    <item>
      <title>GHSA-7j6w-vvw2-5f9c — OpenBao's Kerberos Auth Method Accumulates Unaccessible Tokens</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7j6w-vvw2-5f9c</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/openbao/openbao&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;In OpenBao&amp;#39;s Kerberos auth method on the `GET` handler, or when an `Authorization: Negotiate` header is supplied, the response is includes a `logical.Auth` object in addition to an error message. This results in tokens being created with only the default policy, default TTL, and no entity information, which are hidden by the returned error message. No access to these tokens by the caller occurs and the authentication token is not ever made accessible outside of `sys/raw`. At most this could cause storage usage.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;This is fixed in OpenBao v2.5.4.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Users may set a rate limit quota to limit the creation of these paths. As the path is unauthenticated, it isn&amp;#39;t possible to deny access to it.&lt;/p&gt;
&lt;p&gt;### Reporter&lt;/p&gt;
&lt;p&gt;This was discovered by an anonymous reporter.&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;### Impact&lt;/p&gt;
&lt;p&gt;In OpenBao&amp;#39;s Kerberos auth method on the `GET` handler, or when an `Authorization: Negotiate` header is supplied, the response is includes a `logical.Auth` object in addition to an error message. This results in tokens being created with only the default policy, default TTL, and no entity information, which are hidden by the returned error message. No access to these tokens by the caller occurs and the authentication token is not ever made accessible outside of `sys/raw`. At most this could cause storage usage.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;This is fixed in OpenBao v2.5.4.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Users may set a rate limit quota to limit the creation of these paths. As the path is unauthenticated, it isn&amp;#39;t possible to deny access to it.&lt;/p&gt;
&lt;p&gt;### Reporter&lt;/p&gt;
&lt;p&gt;This was discovered by an anonymous reporter.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7j6w-vvw2-5f9c</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:10835-1 — openbao-2.5.4-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10835-1</link>
      <description>&lt;p&gt;openbao-2.5.4-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;openbao-2.5.4-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:10835-1</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1632 — OpenBao: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1632</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in OpenBao ausnutzen, um Informationen offenzulegen oder einen Denial of Service zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in OpenBao ausnutzen, um Informationen offenzulegen oder einen Denial of Service zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1632</guid>
    </item>
  </channel>
</rss>
