<?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-09-29T10:38:39.396067+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/fkie_cve-2026-71543</id>
    <title>fkie_cve-2026-71543</title>
    <updated>2026-09-29T10:38:39.439061+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, 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.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-71543"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-59w7-v8rr-pr4p</id>
    <title>GHSA-59w7-v8rr-pr4p — OpenBao's Templated Policies Allow Privilege Escalation via Wildcard Characters</title>
    <updated>2026-09-29T10:38:39.439169+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>### ACL Policies</p>
<p>OpenBao supports "templated polices": Policies with placeholders that are replaced at evaluation time.</p>
<p>This allows you to write a single policy which e.g. grants user "alice" access to all entries in a key value engine prefixed with `alice/` while granting "bob" access to `bob/`, "carol" access to `carol/`, etc.</p>
<p>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 "globbing" characters are considered valid ( e.g. `*` is a valid username) they will be able to escalate their privileges.</p>
<p>The problematic characters are `*`, `+` and `/`.</p>
<p>### PKI Secrets Engine `allowed_uri_sans_template` and `allowed_domains` Polices</p>
<p>The PKI secrets engine allows you to limit the "common names" a user can requests a TLS certificate for. Similar to the ACL polices this allows you to restrict e.g. "alice" to  `alice.example.com`, "bob" to  `bob.example.com`, etc. via templates.</p>
<p>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`</p>
<p>The problematic character in this case is `*`.</p>
<p>### SSH Secrets Engine `allowed_users` and `allowed_domains` Polices</p>
<p>The SSH secrets engine allows you to limit the "principal" a user can request as SSH certificate for. Similar to ACL and PKI, this allows templates.</p>
<p>The problematic character in this case…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-59w7-v8rr-pr4p"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2343</id>
    <title>WID-SEC-W-2026-2343 — OpenBao: Mehrere Schwachstellen</title>
    <updated>2026-09-29T10:38:39.439285+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://vulnerability.circl.lu/vuln/wid-sec-w-2026-2343"/>
  </entry>
</feed>
