<?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-04T08:53:51.147322+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:2025-15603</id>
    <title>bdu:2025-15603</title>
    <updated>2026-10-04T08:53:51.268631+00:00</updated>
    <content>bdu:2025-15603</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2025-15603"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bit-openbao-2025-62513</id>
    <title>BIT-openbao-2025-62513 — OpenBao leaks HTTPRawBody in Audit Logs</title>
    <updated>2026-10-04T08:53:51.268701+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. In versions 2.2.0 to 2.4.1, OpenBao's audit log experienced a regression wherein raw HTTP bodies used by few endpoints were not correctly redacted (HMAC'd). This impacts those using the ACME functionality of PKI, resulting in short-lived ACME verification challenge codes being leaked in the audit logs. Additionally, this impacts those using the OIDC issuer functionality of the identity subsystem, auth and token response codes along with claims could be leaked in the audit logs. ACME verification codes are not usable after verification or challenge expiry so are of limited long-term use. This issue has been patched in OpenBao 2.4.2.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-openbao-2025-62513"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-256664</id>
    <title>EUVD-2026-256664</title>
    <updated>2026-10-04T08:53:51.268776+00:00</updated>
    <content>EUVD-2026-256664</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-256664"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-62513</id>
    <title>fkie_cve-2025-62513</title>
    <updated>2026-10-04T08:53:51.268805+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. In versions 2.2.0 to 2.4.1, OpenBao's audit log experienced a regression wherein raw HTTP bodies used by few endpoints were not correctly redacted (HMAC'd). This impacts those using the ACME functionality of PKI, resulting in short-lived ACME verification challenge codes being leaked in the audit logs. Additionally, this impacts those using the OIDC issuer functionality of the identity subsystem, auth and token response codes along with claims could be leaked in the audit logs. ACME verification codes are not usable after verification or challenge expiry so are of limited long-term use. This issue has been patched in OpenBao 2.4.2.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-62513"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-ghfh-fmx4-26h8</id>
    <title>GHSA-ghfh-fmx4-26h8 — OpenBao leaks HTTPRawBody in Audit Logs</title>
    <updated>2026-10-04T08:53:51.268862+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 experienced a regression wherein raw HTTP bodies used by few endpoints were not correctly redacted (HMAC'd).  This impacted the following subsystems:</p>
<p>- When using the ACME functionality of PKI, this would result in short-lived ACME verification challenge codes being leaked in the audit logs.
 - When using the OIDC issuer functionality of the identity subsystem, auth and token response codes along with claims could be leaked in the audit logs.</p>
<p>Third-party plugins may be affected.</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. ACME verification codes are not usable after verification or challenge expiry so are of limited long-term use.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-ghfh-fmx4-26h8"/>
  </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-04T08:53:51.268929+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-04T08:53:51.268969+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>
