<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-01T14:55:50.534615+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/bit-openbao-2026-63132</id>
    <title>BIT-openbao-2026-63132 — OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack</title>
    <updated>2026-10-01T14:55:50.566892+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's handleLogicalRecovery path in http/logical.go compared the highly privileged recovery token with ordinary string equality. A remote unauthenticated attacker able to make repeated recovery mode requests and measure response timing could infer the recovery token. The recovered token could then authorize recovery mode operations that read or modify OpenBao data. This issue is fixed in version 2.6.0.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/bit-openbao-2026-63132"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-63132</id>
    <title>fkie_cve-2026-63132</title>
    <updated>2026-10-01T14:55:50.566989+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's handleLogicalRecovery path in http/logical.go compared the highly privileged recovery token with ordinary string equality. A remote unauthenticated attacker able to make repeated recovery mode requests and measure response timing could infer the recovery token. The recovered token could then authorize recovery mode operations that read or modify OpenBao data. This issue is fixed in version 2.6.0.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-63132"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-34fc-gh42-pj53</id>
    <title>GHSA-34fc-gh42-pj53 — OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack</title>
    <updated>2026-10-01T14:55:50.567047+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>When running in the highly privileged recovery mode, OpenBao was vulnerable to a timing attack against the single recovery token. This allowed an attacker to extract the recovery token and use it to perform operations against the OpenBao instance, including reading or modification of data.</p>
<p>### Patches</p>
<p>This has been patched in OpenBao v2.6.0.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-34fc-gh42-pj53"/>
  </entry>
</feed>
