# CVE-2026-115369: OpenBao 2.5.0 before 2.6.2 PKI allowed_ip_sans_cidr Bypass via CSR IP SANs


- **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** BIT-openbao-2026-115369, GHSA-65vq-mjjr-475v, GHSA-g892-p242-8g86

## What is CVE-2026-115369?

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

### Official description

OpenBao from 2.5.0 before 2.6.2 fails to enforce the PKI role allowed_ip_sans_cidr restriction on IP SANs taken from a CSR when use_csr_sans is enabled. Authenticated callers with sign permission can submit a CSR with an out-of-range IP SAN to pki/sign/<role> and obtain CA-signed certificates for unauthorized IPs.

Weakness: CWE-863 (Incorrect Authorization)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openbao` | Bitnami | From 2.5.0 | 2.6.2 |

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

Upgrade openbao to 2.6.2 or later.

## Is CVE-2026-115369 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- openbao (Bitnami): affected from 2.5.0; fixed in 2.6.2

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

## Sources

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

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