OpenBao Skips Stricter Deny Policy for LIST operations
CVE-2026-63131GHSA-xp3c-3jw3-4vcr
What to do
Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- < 0.0.0-20260713133043-f58d848c139e>= 0.1.0, <= 1.1.5
- Fixed in
- 0.0.0-20260713133043-f58d848c139e
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GO-2026-6579 lists affected ranges: Go github.com/openbao/openbao >=0 =0.1.0
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-xp3c-3jw3-4vcr lists affected ranges: Go github.com/openbao/openbao >=0 =0.1.0 <=1.1.5
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-xp3c-3jw3-4vcr lists affected ranges: Go github.com/openbao/openbao >=0 =0.1.0 <=1.1.5
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 6.0 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2026-63131: 0.48% estimated exploitation activity in the next 30 days; percentile 41.73 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 4 · amended ·
Amended from ghsa record GHSA-xp3c-3jw3-4vcr
- Revision 3 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 2 · amended ·
Amended from osv record GO-2026-6579
- Revision 1 · created ·
Published from osv record GHSA-xp3c-3jw3-4vcr
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-63131 Advisory: OpenBao Skips Stricter Deny Policy for LIST operations IDs: CVE-2026-63131, GHSA-xp3c-3jw3-4vcr Record: https://patchnext.com/advisories/cve-2026-63131 (revision 4, source checked 26 Oct 2026, 15:29 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.0) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Partial vendor fix; fixed versions by package: github.com/openbao/openbao 0.0.0-20260713133043-f58d848c139e. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/openbao/openbao: affected < 0.0.0-20260713133043-f58d848c139e; >= 0.1.0, <= 1.1.5; fixed in 0.0.0-20260713133043-f58d848c139e ## Suggested inspection (read-only) - Go github.com/openbao/openbao: check the installed version with your package manager. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/openbao/openbao. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GO-2026-6579 (OSV record GO-2026-6579 lists affected ranges: Go github.com/openbao/openbao >=0 =0.1.0) - Verified: https://osv.dev/vulnerability/GHSA-xp3c-3jw3-4vcr (OSV record GHSA-xp3c-3jw3-4vcr lists affected ranges: Go github.com/openbao/openbao >=0 =0.1.0 <=1.1.5) - Verified: https://github.com/advisories/GHSA-xp3c-3jw3-4vcr (GitHub-reviewed advisory GHSA-xp3c-3jw3-4vcr lists affected ranges: Go github.com/openbao/openbao >=0 =0.1.0 <=1.1.5) Commands are suggestions: review each one before running it.
Loading voting…