Advisory

GHSA-vv66-6rp4-wr4f

Also known as: BIT-openbao-2026-42186, CVE-2026-42186, GO-2026-5674

Summary

OpenBao's Namespace Deletion May Not Delete Data Properly

Details

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.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-05-05 20:02 UTC
Modified
2026-07-27 09:11 UTC

Affected packages and fixes

github.com/openbao/openbao

Go · All systems

Affected

  • introduced 0, fixed 0.0.0-20260420173541-6d2e0506e2b4 (semver)

Fixed versions

0.0.0-20260420173541-6d2e0506e2b4

Fix

  • Fixed version 0.0.0-20260420173541-6d2e0506e2b4
    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