Skip to content

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

LowCVSS 2.0 EPSS 0.10%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: no · technical impact: partial

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.

Upgrade path

4 packages: 4 fixed.

PackageAffectedFixed inStatus
alpine/openbao(Alpine v3.23) < 2.5.4-r0 2.5.4-r0 Fixed
alpine/openbao(Alpine v3.24) < 2.5.4-r0 2.5.4-r0 Fixed
openbao < 2.5.3; = < 2.5.3 2.5.3 Fixed
openbao(Go) < 0.0.0-20260420160924-abe84e1af4c3 0.0.0-20260420160924-abe84e1af4c3 Fixed

Affected products

ProductAffected versionsFixed in
openbao(Go) < 0.0.0-20260420160924-abe84e1af4c3 0.0.0-20260420160924-abe84e1af4c3
openbao = < 2.5.3 No fix listed
alpine/openbao(Alpine:v3.23) < 2.5.4-r0 2.5.4-r0
alpine/openbao(Alpine:v3.24) < 2.5.4-r0 2.5.4-r0
openbao < 2.5.3 2.5.3

References