---
id: CVE-2026-42186
aliases:
  - GHSA-vv66-6rp4-wr4f
  - BIT-openbao-2026-42186
  - GO-2026-5674
title: OpenBao's Namespace Deletion May Not Delete Data Properly
summary: OpenBao's Namespace Deletion May Not Delete Data Properly
severity: low
vendor: openbao
product: github.com/openbao/openbao
ecosystem: go
affected:
  - github.com/openbao/openbao < 0.0.0-20260420173541-6d2e0506e2b4
patched:
  - github.com/openbao/openbao 0.0.0-20260420173541-6d2e0506e2b4
published: '2026-05-05'
updated: '2026-07-27'
source: OSV
sourceUrl: 'https://osv.dev/vulnerability/GHSA-vv66-6rp4-wr4f'
references:
  - url: 'https://github.com/openbao/openbao/security/advisories/GHSA-vv66-6rp4-wr4f'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2026-42186'
  - url: >-
      https://github.com/openbao/openbao/commit/6d2e0506e2b41be0eaa6643bf7b4efc9a2c09445
  - url: 'https://github.com/openbao/openbao'
  - url: 'https://github.com/openbao/openbao/releases/tag/v2.5.3'
tags:
  - osv
  - go
epss: 0.00432
epssPercentile: 0.34938
ingestedAt: '2026-07-27T19:08:55.200Z'
---

## Overview

### 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.

## Affected packages

- `github.com/openbao/openbao < 0.0.0-20260420173541-6d2e0506e2b4`

## Remediation

Upgrade to a patched release:

- `github.com/openbao/openbao 0.0.0-20260420173541-6d2e0506e2b4`