CVE-2026-39388: OpenBao's Certificate Authentication Allows Token Renewal With Different Certificate
(updated )
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.
References
- github.com/advisories/GHSA-7ccv-rp6m-rffr
- github.com/openbao/openbao/commit/9ab7a066826cc544c30e8b203f8f472076f366e1
- github.com/openbao/openbao/pull/2932
- github.com/openbao/openbao/releases/tag/v2.5.3
- github.com/openbao/openbao/security/advisories/GHSA-7ccv-rp6m-rffr
- nvd.nist.gov/vuln/detail/CVE-2026-39388
Code Behaviors & Features
Detect and mitigate CVE-2026-39388 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →