# CVE-2026-55775: OpenBao improper authorization in System Backend namespace management

Source: https://junglewise.ai/threats/cve-2026-55775-openbao-improper-authorization-in-system-backend-namespace  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-15. Updated: 2026-06-19  
License: CC BY 4.0 with a link back

CVE-2026-55775 · Severity: medium · CVSS 4 · Published 2026-09-15

OpenBao, a tool for managing sensitive data like secrets and keys, contains a vulnerability in how it handles administrative namespaces. An authorized user with limited management permissions within a specific namespace can exploit a naming error to gain unauthorized control over that entire namespace. This could allow the user to view, modify, or delete the namespace, potentially leading to data loss or service disruption within that segment of the organization.

Technologies: [github.com/openbao/openbao (Go)](https://junglewise.ai/threats/technologies/github-com-openbao-openbao), [OpenBao](https://junglewise.ai/threats/technologies/openbao). Vendors: [Go](https://junglewise.ai/threats/vendors/go), [OpenBao](https://junglewise.ai/threats/vendors/openbao).

## Quick answers

**Is CVE-2026-55775 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-55775 being exploited in the wild.

**How severe is CVE-2026-55775?** Medium severity, with a CVSS score of 4, published 15 September 2026.

**Which products and versions are affected?** github.com/openbao/openbao (Go) SEMVER:introduced=0,fixed=0.0.0-20260617103935-d3c1cc64b1ae, SEMVER:introduced=0,fixed=0.0.0-20260617103935-d3c1cc64b1ae,introduced=0.1.0; OpenBao >= 0.1.0, <= 2.5.4.

**Is there a fix for CVE-2026-55775?** Yes. github.com/openbao/openbao (Go): upgrade to 0.0.0-20260617103935-d3c1cc64b1ae or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-55775 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-55775?** Check whether you run github.com/openbao/openbao (Go) or OpenBao at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/openbao/openbao (Go): upgrade to 0.0.0-20260617103935-d3c1cc64b1ae or later

  ```sh
  go get github.com/openbao/openbao@v0.0.0-20260617103935-d3c1cc64b1ae
  ```


## Technical details

An improper authorization vulnerability exists in OpenBao's system backend (/sys/namespaces). The vulnerability stems from the special handling of the literal path 'root', which canonicalizes to an empty string. Because ACL evaluation occurs before this canonicalization, a user granted management capabilities on 'sys/namespaces/root' within a non-root namespace can inadvertently operate on the containing namespace itself. An attacker with low privileges (specifically namespace management rights) can perform operations such as lookup, delete, lock, or patching metadata on their parent namespace. This issue is fixed in OpenBao v2.5.5.

## Affected products

- OpenBao OpenBao >= 0.1.0, <= 2.5.4

## Identifiers

- CVE-2026-55775
- GHSA-mwr2-wmgp-crj6
- GO-2026-5517

## Timeline

- 2026-06-19: advisory: GHSA-mwr2-wmgp-crj6 published
- 2026-06-19: disclosed
- 2026-06-19: patched: Fixed in v2.5.5

## References

- [https://api.github.com/users/satoqz](https://api.github.com/users/satoqz)
- [https://github.com/satoqz](https://github.com/satoqz)
- [https://api.github.com/users/satoqz/gists%7B/gist_id%7D](https://api.github.com/users/satoqz/gists%7B/gist_id%7D)
- [https://api.github.com/users/satoqz/repos](https://api.github.com/users/satoqz/repos)
- [https://avatars.githubusercontent.com/u/40795431?v=4](https://avatars.githubusercontent.com/u/40795431?v=4)
- [https://api.github.com/users/satoqz/events%7B/privacy%7D](https://api.github.com/users/satoqz/events%7B/privacy%7D)

## Related threats

- [OpenBao policy cache incorrect authorization via namespace traversal](https://junglewise.ai/threats/cve-2026-115365-openbao-from-2-3-0-before-2-6-3-contains-an-incorrect)
- [OpenBao ACL bypass in policy denial evaluation](https://junglewise.ai/threats/cve-2026-115361-openbao-before-2-6-3-contains-an-acl-bypass-vulnerability-that)
- [OpenBao Kubernetes Auth token renewal on revoked credentials](https://junglewise.ai/threats/cve-2026-115356-openbao-before-2-6-4-and-2-7-x-before-2-7-1-does-not-verify-when)
- [OpenBao Agent information disclosure via stdout in exec rendering mode](https://junglewise.ai/threats/cve-2026-77285-openbao-agent-information-disclosure-via-stdout-in-exec-rendering)
- [OpenBao recovery mode timing attack token leakage](https://junglewise.ai/threats/cve-2026-63132-openbao-recovery-mode-timing-attack-token-leakage)