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

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

- **Severity:** Low 2.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** BIT-openbao-2026-55774, GHSA-c36x-h252-g9x2, GO-2026-5304

## 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 (Incorrect Authorization)

## Which versions are affected by CVE-2026-55774?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/openbao/openbao` | Go | All versions | 0.0.0-20260617103932-b20b999dd404 |
| `github.com/openbao/openbao` | Go | All versions | 0.0.0-20260617103932-b20b999dd404 |
| `github.com/openbao/openbao` | Go | All versions | 0.0.0-20260617103932-b20b999dd404 |
| `github.com/openbao/openbao` | Go | From 0.1.0 to 2.5.4 | None |
| `github.com/openbao/openbao` | Go | From 0.1.0 to 2.5.4 | None |
| `openbao` | Bitnami | All versions | 2.5.5 |

## How do I fix CVE-2026-55774?

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

## Is CVE-2026-55774 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55774 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-55774 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/openbao/openbao (Go): affected all versions; fixed in 0.0.0-20260617103932-b20b999dd404
- github.com/openbao/openbao (Go): affected all versions; fixed in 0.0.0-20260617103932-b20b999dd404
- github.com/openbao/openbao (Go): affected all versions; fixed in 0.0.0-20260617103932-b20b999dd404
- github.com/openbao/openbao (Go): affected from 0.1.0 up to 2.5.4; no fix listed
- github.com/openbao/openbao (Go): affected from 0.1.0 up to 2.5.4; no fix listed
- openbao (Bitnami): affected all versions; fixed in 2.5.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55774/ (Markdown: https://insights.sbomify.com/CVE-2026-55774/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55774
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55774
- OSV: https://osv.dev/vulnerability/CVE-2026-55774

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55774/
Summaries are generated and may contain mistakes; the official description above is the record.