NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2026-42186: OpenBao's Namespace Deletion May Not Delete Data Properly

lowCVSS 4.0 2.3GHSA-vv66-6rp4-wr4f

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.

Published May 5, 2026 · Updated May 14, 2026

Affected packages

github.com/openbao/openbao

Ecosystem
Go
Affected
< 0.0.0-20260420173541-6d2e0506e2b4
Fixed in
0.0.0-20260420173541-6d2e0506e2b4
Check
go list -m github.com/openbao/openbao

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

Credited to cipherboy.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries