CVE-2026-55774 is a low-severity incorrect authorization vulnerability in github.com/openbao/openbao (go), affecting versions >= 0.1.0, <= 2.5.4. It is fixed in 0.0.0-20260617103932-b20b999dd404.
Summary OpenBao users with access to the sys/leases/revoke/:lease_id endpoint in any namespace can revoke leases in any other namespace as long as the lease identifier is known to them, bypassing ACLs that should apply for cross-namespace revocations. Impact OpenBao's namespaces provide multi-tenant separation. A tenant who intentionally leaks lease identifiers can have their lease and underlying credential revoked by a user in another tenant. Patch This will be fixed in OpenBao v2.5.5. References This vulnerability is similar to but distinct from: CVE-2026-45808 / GHSA-v8v8-cm84-m686 CVE-2026-40264 / GHSA-p49j-v9wc-wg57
The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.
go
github.com/openbao/openbao (>= 0.1.0, <= 2.5.4)github.com/openbao/openbao (< 0.0.0-20260617103932-b20b999dd404)github.com/openbao/openbao → 0.0.0-20260617103932-b20b999dd404 (go)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-55774 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-55774 is reachable in your applications. Get a demo
Upgrade github.com/openbao/openbao to 0.0.0-20260617103932-b20b999dd404 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-55774 is a low-severity incorrect authorization vulnerability in github.com/openbao/openbao (go), affecting versions >= 0.1.0, <= 2.5.4. It is fixed in 0.0.0-20260617103932-b20b999dd404. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
github.com/openbao/openbao (go) versions >= 0.1.0, <= 2.5.4 is affected.
Yes. CVE-2026-55774 is fixed in 0.0.0-20260617103932-b20b999dd404. Upgrade to this version or later.
Whether CVE-2026-55774 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade github.com/openbao/openbao to 0.0.0-20260617103932-b20b999dd404 or later.