github.com/openbao/openbao
Affected
- introduced
0, fixed0.0.0-20260420173541-6d2e0506e2b4(semver)
Fixed versions
0.0.0-20260420173541-6d2e0506e2b4
Fix
- Fixed version
0.0.0-20260420173541-6d2e0506e2b4go get github.com/openbao/[email protected]
Advisory
Also known as: BIT-openbao-2026-42186, CVE-2026-42186, GO-2026-5674
OpenBao's Namespace Deletion May Not Delete Data Properly
Impact
When OpenBao's initial namespace deletion fails, subsequent retries fail to properly remove all data before marking the namespace as deleted. This can affect any outstanding leases as well as potentially leaving unrelated storage entries around.
Patches
This will be patched in OpenBao v2.5.3.
Workarounds
Users may manually remove mounts prior to deleting the namespace.
Audit logs may be used to identify repeated deletion attempts against the same namespace; sys/raw can be used to see what leases were not correctly deleted.
Low Basis: The source's own band: LOW
0, fixed 0.0.0-20260420173541-6d2e0506e2b4 (semver)0.0.0-20260420173541-6d2e0506e2b4
0.0.0-20260420173541-6d2e0506e2b4go 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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0