Vulnerability 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.
Related Weaknesses (CWE)
References
- https://github.com/openbao/openbao/commit/9ba1413d793223cca67db12434093a2f25fdc5
- https://github.com/openbao/openbao/commit/b20b999dd4044d7b419a5472d8fe08407828be
- https://github.com/openbao/openbao/pull/3307
- https://github.com/openbao/openbao/pull/3310
- https://github.com/openbao/openbao/releases/tag/v2.5.5
- https://github.com/openbao/openbao/releases/tag/v2.6.0
- https://github.com/openbao/openbao/security/advisories/GHSA-c36x-h252-g9x2
FAQ
What is CVE-2026-55774?
CVE-2026-55774 is a documented vulnerability. 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 namespac...
How severe is CVE-2026-55774?
CVSS scoring is not yet available for CVE-2026-55774. Check NVD for updates.
Is there a patch for CVE-2026-55774?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.