HighGHSA-59w7-v8rr-pr4pBIT-openbao-2026-71543CVE-2026-71543GO-2026-6556

OpenBao's Templated Policies Allow Privilege Escalation via Wildcard Characters

Published 22 Sept 2026 · Updated 1 Oct 2026

Is your project on an affected github.com/openbao/openbao?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<0.0.0-20260710001938-2d4ebafec5c5
Fixed in
0.0.0-20260710001938-2d4ebafec5c5
Update to the fixed version for your release line, for example:go get github.com/openbao/openbao@v0.0.0-20260710001938-2d4ebafec5c5
Affected
>=0.1.0 <=1.1.5
Fixed in
No fix released

Details

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.

Is GHSA-59w7-v8rr-pr4p in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/openbao/openbao, and gives you the command that fixes it.

More advisories for github.com/openbao/openbao

  • LowCVE-2026-63132OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack in github.com/openbao/openbao · 1 Oct 2026
  • LowCVE-2026-77285OpenBao Agent Writes Secrets to Stdout in github.com/openbao/openbao · 1 Oct 2026
  • LowCVE-2026-63131OpenBao Skips Stricter Deny Policy for LIST operations in github.com/openbao/openbao · 1 Oct 2026
  • MediumCVE-2026-63131OpenBao Skips Stricter Deny Policy for LIST operations · 22 Sept 2026
  • CriticalCVE-2026-63132OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack · 22 Sept 2026
  • LowCVE-2026-77285OpenBao Agent Writes Secrets to Stdout · 22 Sept 2026
All 62 advisories for github.com/openbao/openbao

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.