Is CVE-2026-46358 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-46358 being exploited in the wild.

How severe is CVE-2026-46358?

Medium severity, with a CVSS score of 4, published 28 May 2026.

Which products and versions are affected?

github.com/openbao/openbao (Go) <= 2.5.3, SEMVER:introduced=0, SEMVER:introduced=0,fixed=2.5.4; OpenBao <= 2.5.3.

Is there a fix for CVE-2026-46358?

Yes. github.com/openbao/openbao (Go): upgrade to 2.5.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-46358 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-46358?

Check whether you run github.com/openbao/openbao (Go) or OpenBao at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-46358: OpenBao sensitive information disclosure in audit logs

Q: Is there a fix for CVE-2026-46358?

Yes. github.com/openbao/openbao (Go): upgrade to 2.5.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-46358 attacked?

It is attacked with local access, in a software library.

Q: Am I affected by CVE-2026-46358?

Check whether you run github.com/openbao/openbao (Go) or OpenBao at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-46358 · Severity: medium · CVSS 4 · Published 2026-05-28

OpenBao, an open-source security tool for managing secrets and sensitive data, contains a flaw in its audit logging system. The software incorrectly records authentication headers in cleartext while redacting non-sensitive information. If an attacker gains access to the audit logs, they could obtain credentials and compromise the security of the managed environment.

Technologies: github.com/openbao/openbao (Go), OpenBao. Vendors: Go, OpenBao.

Quick answers

Is CVE-2026-46358 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-46358 being exploited in the wild.
How severe is CVE-2026-46358?: Medium severity, with a CVSS score of 4, published 28 May 2026.
Which products and versions are affected?: github.com/openbao/openbao (Go) <= 2.5.3, SEMVER:introduced=0, SEMVER:introduced=0,fixed=2.5.4; OpenBao <= 2.5.3.
Is there a fix for CVE-2026-46358?: Yes. github.com/openbao/openbao (Go): upgrade to 2.5.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-46358 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-46358?: Check whether you run github.com/openbao/openbao (Go) or OpenBao at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/openbao/openbao (Go): upgrade to 2.5.4 or later
```
go get github.com/openbao/openbao@v2.5.4
```

Technical details

A vulnerability in OpenBao's inline authentication functionality (CWE-532) leads to the improper redaction of sensitive information in audit logs. Specifically, the system removes non-authentication headers while retaining authentication-related headers in cleartext. Exploitation requires an attacker to have high privileges and local access to the audit device or log storage. If successful, an attacker can extract source authentication material from the logs. This issue is fixed in OpenBao version 2.5.4; operators are advised to rotate any potentially leaked credentials.

Affected products

OpenBao OpenBao <= 2.5.3

Identifiers

CVE-2026-46358
GHSA-q8cj-789h-vg24
GO-2026-5574

Timeline

2026-05-21: disclosed
2026-05-28: advisory
2026-05-28: patched: Fixed in v2.5.4

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.