OpenBao's Templated Policies Allow Privilege Escalation via Wildcard Characters

## Impact ### ACL Policies OpenBao supports "templated polices": Policies with placeholders that are replaced at evaluation time. 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. 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. The problematic characters are `*`, `+` and `/`. ### PKI Secrets Engine `allowed_uri_sans_template` and `allowed_domains` Polices 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. 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` The problematic character in this case is `*`. ### SSH Secrets Engine `allowed_users` and `allowed_domains` Polices 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. The problematic character in this case is `,` as the template result is split at all commas and each entry will be allowed. ## Am I affected? You are affected, if a) you use a templated policy (ACL, PKI or SSH) and b) your users can modify data used by your template freely. If you can guarantee that the data used in your templates will never contain the problematic characters, you are not affected. For example, if you use `{{ identity.entity.id }}` in your policy, you are not affected, because `identity.entity.id` is randomly generated by OpenBao. Even with this vulnerability patched: Using user controllable data in your policies is probably not the best idea. ## Patches All three have been patched in OpenBao v2.6.0.

CVSS 4.0

CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Severity from

GitHub (reviewed advisory)

Weakness

CWE-863

Also known as

CVE-2026-71543

• github.com/openbao/openbao/security/advisories/GHSA-59w7-v8rr-pr4p
• nvd.nist.gov/vuln/detail/CVE-2026-71543
• github.com/openbao/openbao/pull/3401
• github.com/openbao/openbao/pull/3473
• github.com/openbao/openbao/commit/2d4ebafec5c524408b3d4ac1198df909cb7ac8c1
• github.com/openbao/openbao/commit/e516ce508e1481504cadbfbf62052364339093bc
• github.com/hashicorp/vault/blob/main/CHANGELOG.md#201
• github.com/openbao/openbao
• github.com/openbao/openbao/releases/tag/v2.6.0