OpenBao's cross-namespace lease revocation via legacy sys/revoke path bypasses ACL

높음 7.1CVE-2026-45808 · BIT-openbao-2026-45808 · GHSA-v8v8-cm84-m686 · Published 07/08/2026 · updated 09/09/2026

요약

CVE-2026-45808은(는) github.com/openbao/openbao에 영향을 주는 높음 (CVSS 7.1) 취약점입니다.
향후 30일 내 악용 확률(EPSS): 0.43%, 전체 취약점의 37.0%보다 높음.
조치: 2.5.4 이상으로 업데이트하세요.

Package	Affected versions	Patched versions
github.com/openbao/openbao Go	`< 2.5.4all versions`	`2.5.4`

Description

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.

NVD 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.