OpenBao's cross-namespace lease revocation via legacy sys/revoke path bypasses ACL
Published 28 May 2026 · Updated 17 Aug 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 package
- Affected
- <2.5.4
- Fixed in
- 2.5.4
go get github.com/openbao/openbao@v2.5.4Details
Impact
OpenBao's namespaces provide multi-tenant separation. A tenant who intentionally leaks lease identifiers can have their lease and underlying credential revoked or renewed by a user in another tenant via the legacy, undocumented sys/revoke and sys/renew endpoints.
Patch
This will be addressed in v2.5.4.
Is GHSA-v8v8-cm84-m686 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
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.