CVE-2026-39388

Low

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.

SeverityLow
CVSS3.1
Exploit probability—
ProductOpenbao
PublishedApr 21, 2026
First seenApr 21, 2026
Weakness typeCWE-295CWE-295

How to fix

Update
  • openbao openbao2.5.3 or later
  • github.com/openbao/openbao0.0.0-20260420160924-abe84e1af4c3 or later

Affected products

ProductAffected versionsFixed in
openbao openbaov < 2.5.32.5.3
github.com/openbao/openbaoGov < 0.0.0-20260420160924-abe84e1af4c30.0.0-20260420160924-abe84e1af4c3

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.

CVE-2026-39388 · Openbao · Dark Radar