OpenBao Skips Stricter Deny Policy for LIST operations

MITTEL 6.0CVE-2026-63131 · BIT-openbao-2026-63131 · GHSA-xp3c-3jw3-4vcr · Published 23/09/2026 · updated 29/09/2026

Kurz gesagt

CVE-2026-63131 ist eine Schwachstelle (MITTEL (CVSS 6.0)) in github.com/openbao/openbao.
Wahrscheinlichkeit einer Ausnutzung in den nächsten 30 Tagen (EPSS): 0.48%, höher als bei 41.7% aller Schwachstellen.
Abhilfe: auf 0.0.0-20260713133043-f58d848c139e oder neuer aktualisieren.

Package	Affected versions	Patched versions
github.com/openbao/openbao Go	`≥ 0.1.0, ≤ 1.1.5≥ 0.1.0< 0.0.0-20260713133043-f58d848c139e`	`0.0.0-20260713133043-f58d848c139e`

Description

Impact

When a policy operator has written capabilities = ["deny"] on a path with a trailing wildcard but allowed a broader list operation (e.g., a deny on secrets/metadata/restricted/* but allowed list on secrets/metadata/*), OpenBao would incorrectly allow the operation. This did not impact other operation types.

Patches

This has been patched in OpenBao v2.6.0.

NVD description

OpenBao is an open source identity-based secrets management system. Prior to 2.6.0, OpenBao's vault/policy/acl.go could evaluate a broader wildcard ACL grant before more-specific trailing-wildcard ACL paths with capabilities = ["deny"] for a LIST operation. When a parent path permitted LIST and a child path was denied, the trailing-slash lookup could therefore allow listing the denied path. Other operation types are outside the repository advisory's affected scope. This issue is fixed in version 2.6.0.