GitHub Advisoryadvisory · Go
GHSA-c36x-h252-g9x2 OpenBao: Cross-namespace lease revocation/renewal via canonical sys/leases/{revoke,renew} — incomplete fix of CVE-2026-45808
LOW
Official page ↗
- Aliases
- CVE-2026-55774
- Ecosystem
- Go
- Packages
- github.com/openbao/openbao
- Severity
- Low
- CVSS vector
- CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
- Weaknesses
- CWE-863
- Reviewed
- 2026-06-19
Affected packages
• Go github.com/openbao/openbao: >= 0.1.0, <= 2.5.4 (no fix yet)
• Go github.com/openbao/openbao: < 0.0.0-20260617103932-b20b999dd404 → fixed in 0.0.0-20260617103932-b20b999dd404
Description
Summary
OpenBao users with access to the `sys/leases/revoke/:lease_id` endpoint in any namespace can revoke leases in any other namespace as long as the lease identifier is known to them, bypassing ACLs that should apply for cross-namespace revocations.
Impact
OpenBao's namespaces provide multi-tenant separation. A tenant who intentionally leaks lease identifiers can have their lease and underlying credential revoked by a user in another tenant.
Patch
This will be fixed in OpenBao v2.5.5.
References
This vulnerability is similar to but distinct from:
• CVE-2026-45808 / GHSA-v8v8-cm84-m686
• CVE-2026-40264 / GHSA-p49j-v9wc-wg57
Related
Alias · CVE (1)
- CVE-2026-55774 OpenBao is an open source identity-based secrets management system. vulnerability
Weakness · CWE (1)
- CWE-863 Incorrect Authorization weakness
References
- https://github.com/openbao/openbao/security/advisories/GHSA-c36x-h252-g9x2 web
- https://github.com/openbao/openbao/pull/3307 web
- https://github.com/openbao/openbao/commit/b20b999dd4044d7b419a5472d8fe08407828be37 web
- https://github.com/openbao/openbao package
- https://github.com/openbao/openbao/releases/tag/v2.5.5 web