OpenBao: Cross-namespace lease revocation/renewal via canonical sys/leases/{revoke,renew} — incomplete fix of CVE-2026-45808
8Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 2.1epss 0.4%
exploitation probability
0.4%top 62% of all CVEs
observed exploitation
nono source reports it
OpenBao is an open source identity-based secrets management system. Prior to 2.5.5, an OpenBao user with access to sys/leases/revoke/:lease_id in one namespace could revoke a lease in another namespace when the foreign lease_id was known, bypassing namespace ACL isolation. The affected lease lookup routing in vault/expiration.go allowed FetchLeaseInfo and loadEntry to resolve cached or stored lease data outside the request namespace, allowing a tenant that intentionally disclosed a lease identifier to have the lease and its underlying credential revoked by another tenant. This issue is fixed in version 2.5.5.
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
Affected products
openbao · openbaoReferences
https://github.com/openbao/openbao/commit/9ba1413d793223cca67db12434093a2f25fdc540https://github.com/openbao/openbao/commit/b20b999dd4044d7b419a5472d8fe08407828be37https://github.com/openbao/openbao/pull/3307https://github.com/openbao/openbao/pull/3310https://github.com/openbao/openbao/releases/tag/v2.5.5https://github.com/openbao/openbao/releases/tag/v2.6.0https://github.com/openbao/openbao/security/advisories/GHSA-c36x-h252-g9x2