OpenBao Skips Stricter Deny Policy for LIST operations

中 6.0CVE-2026-63131 · BIT-openbao-2026-63131 · GHSA-xp3c-3jw3-4vcr · 23/09/2026 公開 · 29/09/2026 更新

要点

CVE-2026-63131 は github.com/openbao/openbao に影響する深刻度「中」 (CVSS 6.0) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.48%（全脆弱性の 41.7% より高い）。
対処：0.0.0-20260713133043-f58d848c139e 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
github.com/openbao/openbao Go	`≥ 0.1.0, ≤ 1.1.5≥ 0.1.0< 0.0.0-20260713133043-f58d848c139e`	`0.0.0-20260713133043-f58d848c139e`

概要

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 の説明

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.