LowGHSA-7ccv-rp6m-rffrBIT-openbao-2026-39388CVE-2026-39388GO-2026-5213

OpenBao's Certificate Authentication Allows Token Renewal With Different Certificate

Published 21 Apr 2026 · Updated 10 Sept 2026

Is your project on an affected github.com/openbao/openbao?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<0.0.0-20260420160924-abe84e1af4c3
Fixed in
0.0.0-20260420160924-abe84e1af4c3
Update to the fixed version for your release line, for example:go get github.com/openbao/openbao@v0.0.0-20260420160924-abe84e1af4c3

Details

Background

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.

Impact

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.

Patches

This has been addressed in v2.5.3.

Workarounds

Ensure privileged roles are tightly scoped to single certificates.

Is GHSA-7ccv-rp6m-rffr in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/openbao/openbao, and gives you the command that fixes it.

More advisories for github.com/openbao/openbao

  • LowCVE-2026-63132OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack in github.com/openbao/openbao · 1 Oct 2026
  • LowCVE-2026-77285OpenBao Agent Writes Secrets to Stdout in github.com/openbao/openbao · 1 Oct 2026
  • LowCVE-2026-71543OpenBao's Templated Policies Allow Privilege Escalation via Wildcard Characters in github.com/openbao/openbao · 1 Oct 2026
  • LowCVE-2026-63131OpenBao Skips Stricter Deny Policy for LIST operations in github.com/openbao/openbao · 1 Oct 2026
  • MediumCVE-2026-63131OpenBao Skips Stricter Deny Policy for LIST operations · 22 Sept 2026
  • CriticalCVE-2026-63132OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack · 22 Sept 2026
All 62 advisories for github.com/openbao/openbao

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.