OpenBao Skips Stricter Deny Policy for LIST operations
## 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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-63131US | —OT elevated | — | ||
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 t… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/hashicorp/vault/blob/main/CHANGELOG.md#203WEB
- https://github.com/openbao/openbaoPACKAGE
- https://github.com/openbao/openbao/commit/2e9625d6cebe4639d051ef53dd6ce7c49914ae6aWEB
- https://github.com/openbao/openbao/commit/f58d848c139e5ba71aa63103fcfe101972b999fcWEB
- https://github.com/openbao/openbao/pull/3389WEB
- https://github.com/openbao/openbao/pull/3474WEB
- https://github.com/openbao/openbao/releases/tag/v2.6.0WEB
- https://github.com/openbao/openbao/security/advisories/GHSA-xp3c-3jw3-4vcrWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan