CVE-2026-55774 OpenBao: Cross-namespace lease revocation/renewal via canonical sys/leases/{revoke,renew} — incomplete fix of CVE-2026-45808

Low 2.1 Published Updated

An attacker in one namespace can revoke leases in another namespace by knowing the lease ID, bypassing isolation and revoking credentials.

Exploited in the wild
Not known
Login needed
An administrator
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-55774?

CVE-2026-55774 is a low-severity missing authorization vulnerability in openbao, published on 15 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

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

Weakness: CWE-863

Which versions are affected by CVE-2026-55774?

6 open source packages ship an affected version, including github.com/openbao/openbao and openbao.

PackageAffectedFixed in
github.com/openbao/openbao GoAll versions0.0.0-20260617103932-b20b999dd404
github.com/openbao/openbao GoAll versions0.0.0-20260617103932-b20b999dd404
github.com/openbao/openbao GoAll versions0.0.0-20260617103932-b20b999dd404
github.com/openbao/openbao GoFrom 0.1.0 to 2.5.4None
github.com/openbao/openbao GoFrom 0.1.0 to 2.5.4None
openbao BitnamiAll versions2.5.5

How do I fix CVE-2026-55774?

Upgrade github.com/openbao/openbao to 0.0.0-20260617103932-b20b999dd404 or later.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-55774 being exploited?

There is no known exploitation of CVE-2026-55774 in the wild and no public exploit code.

Sources

Also known as BIT-openbao-2026-55774, GHSA-c36x-h252-g9x2, GO-2026-5304.

Is CVE-2026-55774 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free