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.
- 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
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
Which versions are affected by CVE-2026-46358?
4 open source packages ship an affected version, including github.com/openbao/openbao and openbao.
| Package | 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.
Sources
Also known as BIT-openbao-2026-46358, GHSA-q8cj-789h-vg24, GO-2026-5574.