# CVE-2026-115361: OpenBao before 2.6.3 ACL Bypass via Dropped Templated Policy Denial


- **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** BIT-openbao-2026-115361, GHSA-fwx5-v4ww-26c8, GHSA-hr5j-3j78-4vh2

## What is CVE-2026-115361?

CVE-2026-115361 is a low-severity vulnerability in openbao, published on 22 Oct 2026. 

### Official description

OpenBao before 2.6.3 contains an ACL bypass vulnerability that silently drops explicit deny rules based on forbidden identity metadata templates within wildcard grants. Attackers whose identity metadata contains wildcard or path segments can access paths that should be denied within the broader wildcard-granted scope.

Weakness: CWE-863 (Incorrect Authorization)

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

1 open source package ship an affected version, including openbao.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openbao` | Bitnami | All versions | 2.6.3 |

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

Upgrade openbao to 2.6.3 or later.

## Is CVE-2026-115361 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115361 is a low-severity vulnerability in openbao, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115361 in the wild and no public exploit code.

Affected packages and fixed versions:
- openbao (Bitnami): affected all versions; fixed in 2.6.3

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-115361/ (Markdown: https://insights.sbomify.com/CVE-2026-115361/index.md)
```

## Sources

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

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