<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 19:11:50 +0000</lastBuildDate>
    <item>
      <title>BIT-openbao-2026-71543 — OpenBao's Templated Policies Allow Privilege Escalation via Wildcard Characters</title>
      <link>https://vulnerability.circl.lu/vuln/bit-openbao-2026-71543</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: openbao&lt;/p&gt;
&lt;p&gt;OpenBao is an open source identity-based secrets management system. Prior to 2.6.0, templated ACL, PKI, and SSH policies could substitute attacker-controlled identity data without rejecting syntax-significant characters. In ACL templated policies, asterisks, plus signs, and slashes could alter path matching. In PKI allowed_uri_sans_template and allowed_domains policies, an asterisk could broaden certificate issuance to unauthorized domains. In SSH allowed_users and allowed_domains policies, a comma could add unauthorized principals. Exploitation requires a deployment to use templated policy data that users can freely modify; templates based on the randomly generated identity.entity.id value are not affected. This could allow privilege escalation, unauthorized access, and unauthorized certificate issuance. This issue is fixed in version 2.6.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: openbao&lt;/p&gt;
&lt;p&gt;OpenBao is an open source identity-based secrets management system. Prior to 2.6.0, templated ACL, PKI, and SSH policies could substitute attacker-controlled identity data without rejecting syntax-significant characters. In ACL templated policies, asterisks, plus signs, and slashes could alter path matching. In PKI allowed_uri_sans_template and allowed_domains policies, an asterisk could broaden certificate issuance to unauthorized domains. In SSH allowed_users and allowed_domains policies, a comma could add unauthorized principals. Exploitation requires a deployment to use templated policy data that users can freely modify; templates based on the randomly generated identity.entity.id value are not affected. This could allow privilege escalation, unauthorized access, and unauthorized certificate issuance. This issue is fixed in version 2.6.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bit-openbao-2026-71543</guid>
    </item>
    <item>
      <title>fkie_cve-2026-71543</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-71543</link>
      <description>&lt;p&gt;OpenBao is an open source identity-based secrets management system. Prior to 2.6.0, templated ACL, PKI, and SSH policies could substitute attacker-controlled identity data without rejecting syntax-significant characters. In ACL templated policies, asterisks, plus signs, and slashes could alter path matching. In PKI allowed_uri_sans_template and allowed_domains policies, an asterisk could broaden certificate issuance to unauthorized domains. In SSH allowed_users and allowed_domains policies, a comma could add unauthorized principals. Exploitation requires a deployment to use templated policy data that users can freely modify; templates based on the randomly generated identity.entity.id value are not affected. This could allow privilege escalation, unauthorized access, and unauthorized certificate issuance. This issue is fixed in version 2.6.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenBao is an open source identity-based secrets management system. Prior to 2.6.0, templated ACL, PKI, and SSH policies could substitute attacker-controlled identity data without rejecting syntax-significant characters. In ACL templated policies, asterisks, plus signs, and slashes could alter path matching. In PKI allowed_uri_sans_template and allowed_domains policies, an asterisk could broaden certificate issuance to unauthorized domains. In SSH allowed_users and allowed_domains policies, a comma could add unauthorized principals. Exploitation requires a deployment to use templated policy data that users can freely modify; templates based on the randomly generated identity.entity.id value are not affected. This could allow privilege escalation, unauthorized access, and unauthorized certificate issuance. This issue is fixed in version 2.6.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-71543</guid>
    </item>
    <item>
      <title>GHSA-59w7-v8rr-pr4p — OpenBao's Templated Policies Allow Privilege Escalation via Wildcard Characters</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-59w7-v8rr-pr4p</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/openbao/openbao&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;### ACL Policies&lt;/p&gt;
&lt;p&gt;OpenBao supports &amp;#34;templated polices&amp;#34;: Policies with placeholders that are replaced at evaluation time.&lt;/p&gt;
&lt;p&gt;This allows you to write a single policy which e.g. grants user &amp;#34;alice&amp;#34; access to all entries in a key value engine prefixed with `alice/` while granting &amp;#34;bob&amp;#34; access to `bob/`, &amp;#34;carol&amp;#34; access to `carol/`, etc.&lt;/p&gt;
&lt;p&gt;If the data used in the template can be controlled by an attacker (e.g. your system allows the user to freely select their username) and &amp;#34;globbing&amp;#34; characters are considered valid ( e.g. `*` is a valid username) they will be able to escalate their privileges.&lt;/p&gt;
&lt;p&gt;The problematic characters are `*`, `+` and `/`.&lt;/p&gt;
&lt;p&gt;### PKI Secrets Engine `allowed_uri_sans_template` and `allowed_domains` Polices&lt;/p&gt;
&lt;p&gt;The PKI secrets engine allows you to limit the &amp;#34;common names&amp;#34; a user can requests a TLS certificate for. Similar to the ACL polices this allows you to restrict e.g. &amp;#34;alice&amp;#34; to  `alice.example.com`, &amp;#34;bob&amp;#34; to  `bob.example.com`, etc. via templates.&lt;/p&gt;
&lt;p&gt;Again, if an attacker can control this data freely, they can trick the PKI engine into using e.g. the `*.example.com` glob effectively allowing them to issue certificates for any subdomain of `example.com`&lt;/p&gt;
&lt;p&gt;The problematic character in this case is `*`.&lt;/p&gt;
&lt;p&gt;### SSH Secrets Engine `allowed_users` and `allowed_domains` Polices&lt;/p&gt;
&lt;p&gt;The SSH secrets engine allows you to limit the &amp;#34;principal&amp;#34; a user can request as SSH certificate for. Similar to ACL and PKI, this allows templates.&lt;/p&gt;
&lt;p&gt;The problematic character in this case…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/openbao/openbao&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;### ACL Policies&lt;/p&gt;
&lt;p&gt;OpenBao supports &amp;#34;templated polices&amp;#34;: Policies with placeholders that are replaced at evaluation time.&lt;/p&gt;
&lt;p&gt;This allows you to write a single policy which e.g. grants user &amp;#34;alice&amp;#34; access to all entries in a key value engine prefixed with `alice/` while granting &amp;#34;bob&amp;#34; access to `bob/`, &amp;#34;carol&amp;#34; access to `carol/`, etc.&lt;/p&gt;
&lt;p&gt;If the data used in the template can be controlled by an attacker (e.g. your system allows the user to freely select their username) and &amp;#34;globbing&amp;#34; characters are considered valid ( e.g. `*` is a valid username) they will be able to escalate their privileges.&lt;/p&gt;
&lt;p&gt;The problematic characters are `*`, `+` and `/`.&lt;/p&gt;
&lt;p&gt;### PKI Secrets Engine `allowed_uri_sans_template` and `allowed_domains` Polices&lt;/p&gt;
&lt;p&gt;The PKI secrets engine allows you to limit the &amp;#34;common names&amp;#34; a user can requests a TLS certificate for. Similar to the ACL polices this allows you to restrict e.g. &amp;#34;alice&amp;#34; to  `alice.example.com`, &amp;#34;bob&amp;#34; to  `bob.example.com`, etc. via templates.&lt;/p&gt;
&lt;p&gt;Again, if an attacker can control this data freely, they can trick the PKI engine into using e.g. the `*.example.com` glob effectively allowing them to issue certificates for any subdomain of `example.com`&lt;/p&gt;
&lt;p&gt;The problematic character in this case is `*`.&lt;/p&gt;
&lt;p&gt;### SSH Secrets Engine `allowed_users` and `allowed_domains` Polices&lt;/p&gt;
&lt;p&gt;The SSH secrets engine allows you to limit the &amp;#34;principal&amp;#34; a user can request as SSH certificate for. Similar to ACL and PKI, this allows templates.&lt;/p&gt;
&lt;p&gt;The problematic character in this case…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-59w7-v8rr-pr4p</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2343 — OpenBao: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2343</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in OpenBao ausnutzen, um seine Privilegien zu erhöhen, Sicherheitsmaßnahmen zu umgehen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in OpenBao ausnutzen, um seine Privilegien zu erhöhen, Sicherheitsmaßnahmen zu umgehen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2343</guid>
    </item>
  </channel>
</rss>
