CVE-2026-42186

high

Published 2026-05-14 · Modified 2026-05-14

💬 Discuss on Community ✚ Propose mitigation

CVSS v3

7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVSS v4 NEW

2.3

CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

VIR risk

7.5

Description

OpenBao's Namespace Deletion May Not Delete Data Properly

Predictions

Exploit likelihood

83%

Patch ETA

—

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.

✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

Package impact

Ecosystem	Package	Vulnerable	Fixed
Go	github.com/openbao/openbao	`<0.0.0-20260420173541-6d2e0506e2b4`	`0.0.0-20260420173541-6d2e0506e2b4`
GO	github.com/openbao/openbao	`< 0.0.0-20260420173541-6d2e0506e2b4`	`0.0.0-20260420173541-6d2e0506e2b4`

Application impact

Vendor	Product	Versions	Fixed
openbao	openbao	`{"endExcluding":"2.5.3"}`	`2.5.3`

References

CWEs

CWE-212

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.