<?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-03T21:41:45.677728+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/bit-openbao-2025-62705</id>
    <title>BIT-openbao-2025-62705 — OpenBao and Vault Leak []byte Fields in Audit Logs</title>
    <updated>2026-10-03T21:41:45.739154+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.4.2, OpenBao's audit log did not appropriately redact fields when relevant subsystems sent []byte response parameters rather than strings. This includes, but is not limited to sys/raw with use of encoding=base64, all data would be emitted unredacted to the audit log, and Transit, when performing a signing operation with a derived Ed25519 key, would emit public keys to the audit log. This issue has been patched in OpenBao 2.4.2.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-openbao-2025-62705"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-256718</id>
    <title>EUVD-2026-256718</title>
    <updated>2026-10-03T21:41:45.739211+00:00</updated>
    <content>EUVD-2026-256718</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-256718"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-62705</id>
    <title>fkie_cve-2025-62705</title>
    <updated>2026-10-03T21:41:45.739256+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.4.2, OpenBao's audit log did not appropriately redact fields when relevant subsystems sent []byte response parameters rather than strings. This includes, but is not limited to sys/raw with use of encoding=base64, all data would be emitted unredacted to the audit log, and Transit, when performing a signing operation with a derived Ed25519 key, would emit public keys to the audit log. This issue has been patched in OpenBao 2.4.2.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-62705"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-rc54-2g2c-g36g</id>
    <title>GHSA-rc54-2g2c-g36g — OpenBao and Vault Leak []byte Fields in Audit Logs</title>
    <updated>2026-10-03T21:41:45.739297+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 audit log did not appropriately redact fields when relevant subsystems sent `[]byte` response parameters rather than `string`s. This includes, but is not limited to:</p>
<p>- `sys/raw` with use of `encoding=base64`, all data would be emitted unredacted to the audit log.
- Transit, when performing a signing operation with a derived Ed25519 key, would emit public keys to the audit log.</p>
<p>Third-party plugins may be affected.</p>
<p>This issue has been present since HashiCorp Vault and continues to impact Vault as of v1.20.4.</p>
<p>### Patches</p>
<p>OpenBao v2.4.2 will patch this issue.</p>
<p>### Workarounds</p>
<p>If users do not use the above functionality, they are not impacted. To prohibit the use of `sys/raw` globally, ensure `raw_storage_endpoint=false` is set or missing from the server configuration.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-rc54-2g2c-g36g"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2025:15663-1</id>
    <title>openSUSE-SU-2025:15663-1 — openbao-2.4.3-1.1 on GA media</title>
    <updated>2026-10-03T21:41:45.739328+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>openbao-2.4.3-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2025:15663-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2391</id>
    <title>WID-SEC-W-2025-2391 — OpenBao: Mehrere Schwachstellen</title>
    <updated>2026-10-03T21:41:45.739346+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in OpenBao ausnutzen, um Informationen offenzulegen, und um einen Denial of Service Angriff durchzuführen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2391"/>
  </entry>
</feed>
