Is CVE-2026-46405 exploited in the wild?

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

How severe is CVE-2026-46405?

Medium severity, with a CVSS score of 5.3, 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-46405?

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-46405 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-46405?

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-46405: OpenBao Kerberos auth method orphaned token accumulation

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

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-46405 attacked?

It is attacked over the network, in a software library.

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

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-46405 · Severity: medium · CVSS 5.3 · Published 2026-05-28

OpenBao, a tool for managing secrets and sensitive data, contains a flaw in its Kerberos authentication method. When certain authentication requests fail, the system inadvertently creates 'orphaned' security tokens that are not accessible to the user but remain in the system's storage. While these tokens cannot be used to access data, a large volume of failed requests could lead to excessive storage consumption and potential performance issues.

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

Quick answers

Is CVE-2026-46405 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-46405 being exploited in the wild.
How severe is CVE-2026-46405?: Medium severity, with a CVSS score of 5.3, 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-46405?: 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-46405 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-46405?: 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 Kerberos auth method occurs when the GET handler or an 'Authorization: Negotiate' header is processed. The component incorrectly returns a 'logical.Auth' object alongside an error message, triggering the creation of a token with default policies and TTLs despite the authentication failure. These tokens are not returned to the caller and are only visible via 'sys/raw', but they persist in the backend storage. An unauthenticated remote attacker could repeatedly trigger this behavior to cause storage exhaustion (CWE-770). The issue is resolved in version 2.5.4 by ensuring the Kerberos auth method does not return an Auth block simultaneously with an error.

Affected products

OpenBao OpenBao <= 2.5.3

Identifiers

CVE-2026-46405
GHSA-7j6w-vvw2-5f9c
GO-2026-5225

Timeline

2026-05-20: patched: Fix merged in pull request 3150
2026-05-21: disclosed: Initial disclosure by maintainers
2026-05-28: advisory: GitHub Advisory published

References

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