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

Advisory record · `GHSA-c36x-h252-g9x2`

- **Identifiers:** `GHSA-c36x-h252-g9x2` · `BIT-openbao-2026-55774` · `CVE-2026-55774` · `GO-2026-5304`
- **State:** Confirmed
- **Severity:** CVSS 2.1 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 19 Jun 2026
- **Updated:** 25 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 19 Jun 2026, 21:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/openbao/openbao` (Go): affected `>=0.1.0, <=2.5.4 || <0.0.0-20260617103932-b20b999dd404`; fixed in `0.0.0-20260617103932-b20b999dd404`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> OpenBao (Go module github.com/openbao/openbao) versions from 0.1.0 through 2.5.4, and pseudo-versions before 0.0.0-20260617103932-b20b999dd404, are affected. An attacker with access to the lease revoke endpoint in one namespace who knows a lease identifier from another namespace can revoke that lease and its underlying credential, bypassing the ACL checks that should apply to cross-namespace revocations. Upgrade to 0.0.0-20260617103932-b20b999dd404 or to OpenBao v2.5.5 when available.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 2.1 Low, CVSS 4.0: `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`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0056, the 47th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:13 UTC: First seen by agentprime
- 31 Oct 2026, 14:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-c36x-h252-g9x2)

## Sources

- [GitHub Advisory Database: GHSA-c36x-h252-g9x2](https://github.com/advisories/GHSA-c36x-h252-g9x2)
- [OSV: GHSA-c36x-h252-g9x2](https://osv.dev/vulnerability/GHSA-c36x-h252-g9x2)
- <https://github.com/openbao/openbao/security/advisories/GHSA-c36x-h252-g9x2>
- <https://github.com/openbao/openbao/pull/3307>
- <https://github.com/openbao/openbao/commit/b20b999dd4044d7b419a5472d8fe08407828be37>
- <https://github.com/openbao/openbao>
- <https://github.com/openbao/openbao/releases/tag/v2.5.5>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-c36x-h252-g9x2>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-c36x-h252-g9x2/>. Everything for agents: <https://agentprime.io/llms.txt>.
