<?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-10-03T08:00:51.352050+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/bdu:2026-10829</id>
    <title>bdu:2026-10829</title>
    <updated>2026-10-03T08:00:51.423937+00:00</updated>
    <content>bdu:2026-10829</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2026-10829"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bit-openbao-2026-45808</id>
    <title>BIT-openbao-2026-45808 — OpenBao's cross-namespace lease revocation via legacy sys/revoke path bypasses ACL</title>
    <updated>2026-10-03T08:00:51.423972+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: openbao</p>
<p>OpenBao is an open source identity-based secrets management system. Prior to version 2.5.4, OpenBao's namespaces provide multi-tenant separation. A tenant who intentionally leaks lease identifiers can have their lease and underlying credential revoked or renewed by a user in another tenant via the legacy, undocumented `sys/revoke` and `sys/renew` endpoints. This is fixed in OpenBao v2.5.4.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-openbao-2026-45808"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cleanstart-2026-kk55331</id>
    <title>Withdrawn: CLEANSTART-2026-KK55331 — Previously, after a channel has been established, a malicious peer could send crafted messages that would deadlock the…</title>
    <updated>2026-10-03T08:00:51.424009+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Withdrawn by the publisher.</strong></p>
<p><strong>Affected:</strong> CleanStart: dex</p>
<p>Multiple security vulnerabilities affect the dex package. Previously, after a channel has been established, a malicious peer could send crafted messages that would deadlock the entire connection. See references for individual vulnerability details.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2026-kk55331"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-352290</id>
    <title>EUVD-2026-352290</title>
    <updated>2026-10-03T08:00:51.424034+00:00</updated>
    <content>EUVD-2026-352290</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-352290"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-45808</id>
    <title>fkie_cve-2026-45808</title>
    <updated>2026-10-03T08:00:51.424047+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>OpenBao is an open source identity-based secrets management system. Prior to version 2.5.4, OpenBao's namespaces provide multi-tenant separation. A tenant who intentionally leaks lease identifiers can have their lease and underlying credential revoked or renewed by a user in another tenant via the legacy, undocumented `sys/revoke` and `sys/renew` endpoints. This is fixed in OpenBao v2.5.4.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-45808"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-v8v8-cm84-m686</id>
    <title>GHSA-v8v8-cm84-m686 — OpenBao's cross-namespace lease revocation via legacy sys/revoke path bypasses ACL</title>
    <updated>2026-10-03T08:00:51.424070+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/openbao/openbao</p>
<p># Impact</p>
<p>OpenBao's namespaces provide multi-tenant separation. A tenant who intentionally leaks lease identifiers can have their lease and underlying credential revoked or renewed by a user in another tenant via the legacy, undocumented `sys/revoke` and `sys/renew` endpoints.</p>
<p># Patch</p>
<p>This will be addressed in v2.5.4.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-v8v8-cm84-m686"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10835-1</id>
    <title>openSUSE-SU-2026:10835-1 — openbao-2.5.4-1.1 on GA media</title>
    <updated>2026-10-03T08:00:51.424092+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>openbao-2.5.4-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2026:10835-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1640</id>
    <title>WID-SEC-W-2026-1640 — OpenBao: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen</title>
    <updated>2026-10-03T08:00:51.424109+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in OpenBao ausnutzen, um Sicherheitsvorkehrungen zu umgehen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1640"/>
  </entry>
</feed>
