# CVE-2026-46358: OpenBao's Inline Auth Incorrectly Redacted Headers

> OpenBao incorrectly redacts audit logs, exposing authentication headers in cleartext to attackers with audit device access.

- **Severity:** Medium 5.4 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** BIT-openbao-2026-46358, GHSA-q8cj-789h-vg24, GO-2026-5574

## What is CVE-2026-46358?

CVE-2026-46358 is a medium-severity vulnerability in openbao, published on 7 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

OpenBao is an open source identity-based secrets management system. Prior to version 2.5.4, OpenBao's inline auth functionality incorrectly redacted audit log entries, resulting in non-auth headers being removed and auth-related headers being retained in cleartext. This requires an attacker to compromise access to the audit device. Operators should review leaked source authentication material and rotate it as appropriate. This is fixed in OpenBao v2.5.4.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

4 open source packages ship an affected version, including github.com/openbao/openbao and openbao.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/openbao/openbao` | Go | All versions | None |
| `github.com/openbao/openbao` | Go | All versions | 2.5.4 |
| `github.com/openbao/openbao` | Go | All versions | 2.5.4 |
| `openbao` | Bitnami | All versions | 2.5.4 |

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

Upgrade github.com/openbao/openbao to 2.5.4 or later.

## Is CVE-2026-46358 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46358 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46358 is a medium-severity vulnerability in openbao, published on 7 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46358 exists.

Affected packages and fixed versions:
- github.com/openbao/openbao (Go): affected all versions; no fix listed
- github.com/openbao/openbao (Go): affected all versions; fixed in 2.5.4
- github.com/openbao/openbao (Go): affected all versions; fixed in 2.5.4
- openbao (Bitnami): affected all versions; fixed in 2.5.4

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

## Sources

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

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