OpenBao's cross-namespace lease revocation via legacy sys/revoke path bypasses ACL
cve-program · CVE-2026-45808
PublishedOpenBao 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.
Read the publisher's advisoryeuvd · EUVD-2026-54684
PublishedOpenBao 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.
Read the publisher's advisorynvd · CVE-2026-45808
PublishedOpenBao 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.
Read the publisher's advisoryosv · GHSA-v8v8-cm84-m686
Published# 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.
Read the publisher's advisoryosv · GO-2026-5657
PublishedOpenBao's cross-namespace lease revocation via legacy sys/revoke path bypasses ACL in github.com/openbao/openbao. NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions. (If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.) The additional affected modules and versions are: github.com/openbao/openbao before v2.5.4.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-45808 · CVE overview and exploitation status
cve-program · CVE-2026-45808
- https://github.com/openbao/openbao/security/advisories/GHSA-v8v8-cm84-m686
- https://github.com/openbao/openbao/pull/3152
- https://github.com/openbao/openbao/commit/c0495646b41cea0e3f5a1030132e9cf5c2375b5c
- https://github.com/openbao/openbao/releases/tag/v2.5.4
euvd · EUVD-2026-54684
- https://github.com/openbao/openbao/security/advisories/GHSA-v8v8-cm84-m686
- https://github.com/openbao/openbao/pull/3152
- https://github.com/openbao/openbao/commit/c0495646b41cea0e3f5a1030132e9cf5c2375b5c
- https://github.com/openbao/openbao/releases/tag/v2.5.4
nvd · CVE-2026-45808
- https://github.com/openbao/openbao/commit/c0495646b41cea0e3f5a1030132e9cf5c2375b5c
- https://github.com/openbao/openbao/pull/3152
- https://github.com/openbao/openbao/releases/tag/v2.5.4
- https://github.com/openbao/openbao/security/advisories/GHSA-v8v8-cm84-m686
osv · GHSA-v8v8-cm84-m686
- https://github.com/openbao/openbao/security/advisories/GHSA-v8v8-cm84-m686
- https://github.com/openbao/openbao/pull/3152
- https://github.com/openbao/openbao/commit/c0495646b41cea0e3f5a1030132e9cf5c2375b5c
- https://github.com/openbao/openbao
- https://github.com/openbao/openbao/releases/tag/v2.5.4