<?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-03T00:24:19.632122+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-2026-77285</id>
    <title>BIT-openbao-2026-77285 — OpenBao Agent Writes Secrets to Stdout</title>
    <updated>2026-10-03T00:24:19.686780+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 2.6.0, OpenBao Agent's exec rendering mode could write secrets from env_template to standard output when command/agent/exec/exec.go re-created the template runner after repeated rendering failures, primarily after num_retries was reached. A process supervisor, log collector, or local user able to read that output could obtain the rendered secret values. This issue is fixed in version 2.6.0.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-openbao-2026-77285"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-374350</id>
    <title>EUVD-2026-374350</title>
    <updated>2026-10-03T00:24:19.686835+00:00</updated>
    <content>EUVD-2026-374350</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-374350"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-77285</id>
    <title>fkie_cve-2026-77285</title>
    <updated>2026-10-03T00:24:19.686852+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 2.6.0, OpenBao Agent's exec rendering mode could write secrets from env_template to standard output when command/agent/exec/exec.go re-created the template runner after repeated rendering failures, primarily after num_retries was reached. A process supervisor, log collector, or local user able to read that output could obtain the rendered secret values. This issue is fixed in version 2.6.0.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-77285"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-444v-8vxr-p36h</id>
    <title>GHSA-444v-8vxr-p36h — OpenBao Agent Writes Secrets to Stdout</title>
    <updated>2026-10-03T00:24:19.686877+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>During certain error conditions, OpenBao Agent's exec rendering mode will incorrectly write secrets specified in `env_template` to stdout. This primarily happens when `num_retries` is met.</p>
<p>This vulnerability is original to Vault and was reported via the OpenBao security mailing list.</p>
<p>### Patches</p>
<p>This is addressed in OpenBao v2.6.0 GA.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-444v-8vxr-p36h"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2343</id>
    <title>WID-SEC-W-2026-2343 — OpenBao: Mehrere Schwachstellen</title>
    <updated>2026-10-03T00:24:19.686903+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in OpenBao ausnutzen, um seine Privilegien zu erhöhen, Sicherheitsmaßnahmen zu umgehen oder vertrauliche Informationen offenzulegen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2343"/>
  </entry>
</feed>
