Advisory

GHSA-7ccv-rp6m-rffr

Also known as: BIT-openbao-2026-39388, CVE-2026-39388, GO-2026-5213

Summary

OpenBao's Certificate Authentication Allows Token Renewal With Different Certificate

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.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-04-21 17:26 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/openbao/openbao

Go · All systems

Affected

  • introduced 0, fixed 0.0.0-20260420160924-abe84e1af4c3 (semver)

Fixed versions

0.0.0-20260420160924-abe84e1af4c3

Fix

  • Fixed version 0.0.0-20260420160924-abe84e1af4c3
    go get github.com/openbao/[email protected]

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences