Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2026-55775 — openbao

🟢 CVSS 2.0 — Low ✅ No Known Exploit CWE-285 OSV
2.0
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

OpenBao's System Backend allows Unauthorized Management of the containing Namespace

Summary

A user that is granted namespace management (/sys/namespaces) capabilities within a non-root namespace ("the victim namespace") can abuse special handling of the literal path "root" in namespace path canonicalization to manage the victim namespace itself.

Details

Several endpoints under /sys/namespaces/* accept a namespace path segment that is canonicalized and then appended to the path of the sys mount's containing namespace (set via path prefix or X-Vault-Namespace header) to determine the absolute path of the namespace to operate on.

Given the special namespace path "root" canonicalizes to en empty path (""), when passed as /sys/namespaces/root, the resulting absolute namespace path remains equal to the sys mount's containing namespace. Given ACLs are evaluated before namespace path canonicalization, this allows users with capabilities on /sys/namespaces/root within any given namespace to operate on the namespace itself instead.

Impact

Users that were granted the required capabilities can abuse this vulnerability to:

  • Look up
  • Delete
  • Lock
  • Patch custom metadata

against the namespace containing the system backend they can manage sys/namespaces/root in. The exact range of operations that can be performed depends on the specific capabilities granted on said path and any sub-paths such as /api-lock.

Notably, the root namespace is immutable and cannot be modified, deleted or locked, and is thus unaffected. Also note that users can only abuse this vulnerability to operate on the direct parent or "containing" namespace relative to their capabilities, not arbitrary namespaces.

Patch

This will be fixed in OpenBao v2.5.5.

PoC

Start a development server:

```sh

bao server -dev

```

Create a namespace:

```sh

bao namespace create victim

```

This will be the namespace we gain unauthorized management of.

Create a policy that allows management of namespaces, _inside_ of the victim

namespace.

```sh

bao policy write -namespace=victim namespace-management - <<EOF

path "sys/namespaces/*" {

capabilities = ["read", "update", "patch", "delete"]

}

EOF

```

Then create a token with above policy attached:

```sh

export BAO_TOKEN=$(bao token create -namespace=victim -policy=namespace-management -field=token)

```

Operate on the victim's namespace using the token, for example by outright deleting it:

```sh

bao namespace delete -namespace=victim root

```

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. Rated impact: confidentiality none, integrity low, availability low.

CVSS metrics in full

The score comes from this vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Attack requirements: Present — the target has to be in a particular state for the attack to work.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Confidentiality impact: None.
  • Integrity impact: Low — limited, and the attacker does not choose what is affected.
  • Availability impact: Low — limited, and the attacker does not choose what is affected.

Weakness class

CVE-2026-55775 is classified as CWE-285: Improper Authorization. A request is carried out without confirming that the caller is permitted to perform it on that specific resource.

Affected software

CVE-2026-55775 is recorded against 1 package.

  • github.com/openbao/openbao

Timeline and source

Published on 25 June 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from OSV.

References

github.com (Advisory)
github.com (Fix)
github.com (Web)

Other advisories for this package

github.com/openbao/openbao has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-285: Improper Authorization) in other software:

Details

Severity LOW
CVSS Score 2.0
CVSS Vector CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N
CWE CWE-285
Public Exploit ✅ No
Source OSV
Published 2026-06-25
Updated 2026-08-20
Modified 2026-06-25

Affected Packages

Software From version Fixed in
github.com/openbao/openbao — —

Similar Threats

Free Vulnerability Check

Is your site affected by CVE-2026-55775?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against CVE-2026-55775 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2026
✓