Low severity · published Sep 15, 2026
CVE-2026-55774
OpenBao: Cross-namespace lease revocation/renewal via canonical sys/leases/{revoke,renew} — incomplete fix of CVE-2026-45808
2.1
CVSS
0.6%
EPSS
No
On KEV
Description
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.
Exploitation
Is it being used?
Exploit prediction (EPSS)0.6% · higher than 47% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
OP
openbao · openbao
< 2.5.5 · source: vendor
Affected product
OP
openbao
openbao
More from openbao
9.8
CVE-2024-2048
Vault and Vault Enterprise (“Vault”) TLS certificate auth method did not correctly validate client certificates when configured with a non-CA certificate as trusted certificate
9.2
CVE-2026-63132
OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack
9.1
CVE-2025-54997
OpenBao: Privileged Operator May Execute Code on the Underlying Host
8.8
CVE-2024-7594
Vault’s SSH secrets engine did not require the valid_principals list to contain a value by default
8.3
CVE-2026-33757
OpenBao lacks user confirmation for OIDC direct callback mode