Is CVE-2026-40264 exploited in the wild?

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

How severe is CVE-2026-40264?

Medium severity, with a CVSS score of 4, published 21 April 2026.

Which products and versions are affected?

github.com/openbao/openbao (Go) < 0.0.0-20260420162526-f58111d2ca54, SEMVER:introduced=0,fixed=0.0.0-20260420162526-f58111d2ca54.

Is there a fix for CVE-2026-40264?

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

Am I affected by CVE-2026-40264?

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-40264: OpenBao's Token Store Allows Cross-Namespace Renewal, Revocation

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

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

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

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-40264 · Severity: medium · CVSS 4 · Published 2026-04-21

OpenBao is an open source identity-based secrets management system. OpenBao's namespaces provide multi-tenant separation. Prior to version 2.5.3, a tenant who leaks token accessors can have their token revoked or renewed by a privileged administrator in another tenant. This is addressed in v2.5.3.

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

Quick answers

Is CVE-2026-40264 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-40264 being exploited in the wild.
How severe is CVE-2026-40264?: Medium severity, with a CVSS score of 4, published 21 April 2026.
Which products and versions are affected?: github.com/openbao/openbao (Go) < 0.0.0-20260420162526-f58111d2ca54, SEMVER:introduced=0,fixed=0.0.0-20260420162526-f58111d2ca54.
Is there a fix for CVE-2026-40264?: Yes. github.com/openbao/openbao (Go): upgrade to 0.0.0-20260420162526-f58111d2ca54 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-40264?: 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 0.0.0-20260420162526-f58111d2ca54 or later
```
go get github.com/openbao/openbao@v0.0.0-20260420162526-f58111d2ca54
```

Affected products

github.com/openbao/openbao (Go) < 0.0.0-20260420162526-f58111d2ca54, SEMVER:introduced=0,fixed=0.0.0-20260420162526-f58111d2ca54
OpenBao

Identifiers

CVE-2026-40264
GHSA-p49j-v9wc-wg57
GO-2026-5526

References

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