<?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-02T19:34:56.226897+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-52893</id>
    <title>BIT-openbao-2025-52893 — OpenBao May Leak Sensitive Information in Logs When Processing Malformed Data</title>
    <updated>2026-10-02T19:34:56.304238+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: openbao</p>
<p>OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys. OpenBao before v2.3.0 may leak sensitive information in logs when processing malformed data. This is separate from the earlier HCSEC-2025-09 / CVE-2025-4166. This issue has been fixed in OpenBao v2.3.0 and later. Like with HCSEC-2025-09, there is no known workaround except to ensure properly formatted requests from all clients.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-openbao-2025-52893"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cleanstart-2026-da82476</id>
    <title>Withdrawn: CLEANSTART-2026-DA82476 — Security fixes in fulcio 1.7.1-r0</title>
    <updated>2026-10-02T19:34:56.304293+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: fulcio</p>
<p>Package fulcio version 1.7.1-r0 fixes 6 vulnerabilities: CVE-2025-11065, CVE-2026-41178, CVE-2025-52893, ghsa-hrxh-6v49-42gf, ghsa-2464-8j7c-4cjm...</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2026-da82476"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cnvd-2025-18641</id>
    <title>cnvd-2025-18641</title>
    <updated>2026-10-02T19:34:56.304316+00:00</updated>
    <content>cnvd-2025-18641</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2025-18641"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-245877</id>
    <title>EUVD-2026-245877</title>
    <updated>2026-10-02T19:34:56.304331+00:00</updated>
    <content>EUVD-2026-245877</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-245877"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-52893</id>
    <title>fkie_cve-2025-52893</title>
    <updated>2026-10-02T19:34:56.304342+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys. OpenBao before v2.3.0 may leak sensitive information in logs when processing malformed data. This is separate from the earlier HCSEC-2025-09 / CVE-2025-4166. This issue has been fixed in OpenBao v2.3.0 and later. Like with HCSEC-2025-09, there is no known workaround except to ensure properly formatted requests from all clients.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-52893"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-8f5r-8cmq-7fmq</id>
    <title>GHSA-8f5r-8cmq-7fmq — OpenBao Inserts Sensitive Information into Log File when processing malformed data</title>
    <updated>2026-10-02T19:34:56.304364+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/openbao/openbao/sdk/v2</p>
<p>### Impact</p>
<p>OpenBao before v2.3.0 and HashiCorp Vault as of the current v1.19.5 may leak sensitive information in logs when processing malformed data. This is separate from the earlier HCSEC-2025-09 / CVE-2025-4166.</p>
<p>### Patches</p>
<p>This issue has been fixed in OpenBao v2.3.0 and later.</p>
<p>### Workarounds</p>
<p>Like with HCSEC-2025-09, there is no known workaround except to ensure properly formatted requests from all clients.</p>
<p>### Remediation</p>
<p>Users with the capability to search through server and audit logs for any possible exposed secrets can refer to the following snippets to aid in searching:</p>
<p>Audit Log</p>
<p>```
... "error":"error converting input for field \"password\": expected type 'string', got unconvertible type 'map[string]interface {}', value: '&lt;sensitive data&gt;'" ...
```</p>
<p>Server Log</p>
<p>```
error converting input for field "password": expected type 'string', got unconvertible type 'map[string]interface {}', value: '&lt;sensitive data&gt;'
```</p>
<p>If any matches are found, rotating the affected secret is advised.</p>
<p>### References</p>
<p>See also: https://discuss.hashicorp.com/t/hcsec-2025-09-vault-may-expose-sensitive-information-in-error-logs-when-processing-malformed-data-with-the-kv-v2-plugin/74717</p>
<p>See also: https://github.com/go-viper/mapstructure/releases/tag/v2.3.0</p>
<p>See also: https://github.com/go-viper/mapstructure/pull/105 -&gt; https://github.com/go-viper/mapstructure/commit/ed3f92181528ff776a0324107b8b55026e93766a</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-8f5r-8cmq-7fmq"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2025:15254-1</id>
    <title>openSUSE-SU-2025:15254-1 — openbao-2.3.1-1.1 on GA media</title>
    <updated>2026-10-02T19:34:56.304403+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>openbao-2.3.1-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2025:15254-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-52893</id>
    <title>UBUNTU-CVE-2025-52893</title>
    <updated>2026-10-02T19:34:56.304420+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:25.10: golang-github-go-viper-mapstructure, Ubuntu:26.04:LTS: golang-github-go-viper-mapstructure</p>
<p>OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys. OpenBao before v2.3.0 may leak sensitive information in logs when processing malformed data. This is separate from the earlier HCSEC-2025-09 / CVE-2025-4166. This issue has been fixed in OpenBao v2.3.0 and later. Like with HCSEC-2025-09, there is no known workaround except to ensure properly formatted requests from all clients.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-52893"/>
  </entry>
</feed>
