CVE-2026-45808 OpenBao's cross-namespace lease revocation via legacy sys/revoke path bypasses ACL
Attackers can revoke or renew other tenants' credentials via legacy endpoints, bypassing namespace ACLs in OpenBao.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-45808?
CVE-2026-45808 is a high-severity missing authorization vulnerability in openbao, published on 7 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
OpenBao is an open source identity-based secrets management system. Prior to version 2.5.4, 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. This is fixed in OpenBao v2.5.4.
Weakness: CWE-863
Which versions are affected by CVE-2026-45808?
4 open source packages ship an affected version, including github.com/openbao/openbao and openbao.
| Package | Affected | Fixed in |
|---|---|---|
github.com/openbao/openbao Go | All versions | None |
github.com/openbao/openbao Go | All versions | 2.5.4 |
github.com/openbao/openbao Go | All versions | 2.5.4 |
openbao Bitnami | All versions | 2.5.4 |
How do I fix CVE-2026-45808?
Upgrade github.com/openbao/openbao to 2.5.4 or later.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-45808 being exploited?
There is no known exploitation of CVE-2026-45808 in the wild and no public exploit code.
Sources
Also known as BIT-openbao-2026-45808, CLEANSTART-2026-OD55795, GHSA-v8v8-cm84-m686, GO-2026-5657.