Privileged OpenBao Operator May Execute Code on the Underlying Host
Published 8 Aug 2025 · Updated 27 Jul 2026
Is your project on an affected github.com/openbao/openbao?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=0.1.0 <2.3.2
- Fixed in
- 2.3.2
go get github.com/openbao/openbao@v2.3.2- Affected
- <0.0.0-20250806194004-a14053c9679d
- Fixed in
- 0.0.0-20250806194004-a14053c9679d
go get github.com/openbao/openbao@v0.0.0-20250806194004-a14053c9679dDetails
Impact
Under certain threat models, OpenBao operators with privileged API access may not be system administrators and thus normally lack the ability to update binaries or execute code on the system. Additionally, privileged API operators should be unable to perform TCP connections to arbitrary hosts in the environment OpenBao is executing within. The API-driven audit subsystem granted privileged API operators the ability to do both with an attacker-controlled log prefix. Access to these endpoints should be restricted.
Patches
OpenBao v2.3.2 will patch this issue.
Workarounds
Users may deny all access to the sys/audit/* interface (with create and update) permission via policies with explicit deny grants. This would not restrict root level operators, however, for whom there are no workarounds.
This interface allowed arbitrary filesystem and network (write) access as the user the OpenBao server was running as; in conjunction with allowing custom plugins or other system processes this may enable code execution.
References
This issue was disclosed to HashiCorp and is the OpenBao equivalent of the following tickets:
- https://discuss.hashicorp.com/t/hcsec-2025-14-privileged-vault-operator-may-execute-code-on-the-underlying-host/76033
- https://nvd.nist.gov/vuln/detail/CVE-2025-6000
Is GHSA-xp75-r577-cvhp 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-71543OpenBao's Templated Policies Allow Privilege Escalation via Wildcard Characters 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
References
- Linkgithub.com/openbao/openbao/security/advisories/GHSA-xp75-r577-cvhp
- Advisorynvd.nist.gov/vuln/detail/CVE-2025-54997
- Advisorynvd.nist.gov/vuln/detail/CVE-2025-6000
- Linkgithub.com/openbao/openbao/pull/1634
- Linkgithub.com/openbao/openbao/commit/a14053c9679d6e9cf370f00cf933476cda6d84a2
- Linkdiscuss.hashicorp.com/t/hcsec-2025-14-privileged-vault-operator-may-execute-code-on-the-underlying-host/76033
- Packagegithub.com/openbao/openbao
- Linkgithub.com/openbao/openbao/releases/tag/v2.3.2
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.