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 originally from HashiCorp Vault.
This has been addressed in v2.5.3.
Ensure privileged roles are tightly scoped to single certificates.
| Score | Percentile |
|---|---|
| 0.02% | 6.79% |
| Base score | Version | Severity | Vector |
|---|---|---|---|
| 3.1 | 3.1 | — |
|
| 2.0 | 4.0 | — |
|
| Type | Value |
|---|---|
| GHSA | GHSA-7ccv-rp6m-rffr ↗ |
| CVE | CVE-2026-39388 ↗ |
Vulnerable version ranges and first patched releases as published by GitHub.
| Ecosystem | Package | Vulnerable range | First patched | Vulnerable functions |
|---|---|---|---|---|
| go | github.com/openbao/openbao | < 0.0.0-20260420160924-abe84e1af4c3 | 0.0.0-20260420160924-abe84e1af4c3 | — |