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

What is CVE-2026-42186?

CVE-2026-42186 is a low-severity vulnerability in openbao, published on 14 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

OpenBao is an open source identity-based secrets management system. Prior to 2.5.3, 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. This vulnerability is fixed in 2.5.3.

Weakness: CWE-212

Which versions are affected by CVE-2026-42186?

4 open source packages ship an affected version, including github.com/openbao/openbao and openbao. It affects 1 product.

Products include Openbao Openbao.

How do I fix CVE-2026-42186?

Upgrade github.com/openbao/openbao to 0.0.0-20260420173541-6d2e0506e2b4 or later.

Is CVE-2026-42186 being exploited?

There is no known exploitation of CVE-2026-42186 in the wild and no public exploit code.

Other vulnerabilities in openbao

• CVE-2026-33757 OpenBao lacks user confirmation for OIDC direct callback mode Critical 9.6
• CVE-2026-33758 OpenBao has Reflected XSS in its OIDC authentication error message Critical 9.4
• CVE-2025-54997 OpenBao: Privileged Operator May Execute Code on the Underlying Host Critical 9.1
• CVE-2025-64761 OpenBao Privileged Operator Identity Group Root Escalation High 7.5
• CVE-2025-59043 OpenBao vulnerable to denial of service via malicious JSON request processing High 7.5

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as BIT-openbao-2026-42186, GHSA-vv66-6rp4-wr4f, GO-2026-5674.