Not available
Medium
github.com/openbao/openbao

CVE-2026-46358

CVE-2026-46358 is a medium-severity security vulnerability in github.com/openbao/openbao (go), affecting versions <= 2.5.3. It is fixed in 2.5.4.

Key facts
CVSS score
Not available
Medium
Attack vector
Not available
Issuing authority
GitHub Advisory Database
Affected package
github.com/openbao/openbao
Fixed in
2.5.4
Disclosed
2026

Summary

Impact 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. Patches This is fixed in OpenBao v2.5.4. Resources https://github.com/openbao/openbao/issues/3074

Impact

Not available

Affected versions

go

  • github.com/openbao/openbao (<= 2.5.3)

Security releases

  • github.com/openbao/openbao → 2.5.4 (go)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-46358 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-46358 is reachable in your applications. Get a demo

Remediation advice

Upgrade github.com/openbao/openbao to 2.5.4 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-46358

What is CVE-2026-46358?

CVE-2026-46358 is a medium-severity security vulnerability in github.com/openbao/openbao (go), affecting versions <= 2.5.3. It is fixed in 2.5.4.

Which versions of github.com/openbao/openbao are affected by CVE-2026-46358?

github.com/openbao/openbao (go) versions <= 2.5.3 is affected.

Is there a fix for CVE-2026-46358?

Yes. CVE-2026-46358 is fixed in 2.5.4. Upgrade to this version or later.

Is CVE-2026-46358 exploitable, and should I be worried?

Whether CVE-2026-46358 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-46358 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-46358?

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

Stop the waste.
Protect your environment with Kodem.