Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

OpenBao's Templated Policies Allow Privilege Escalation via Wildcard Characters

CVE-2026-71543GHSA-59w7-v8rr-pr4p

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.

Add to your agent

Affected packages

  • Go github.com/openbao/openbao

    Affected
    < 0.0.0-20260710001938-2d4ebafec5c5>= 0.1.0, <= 1.1.5
    Fixed in
    0.0.0-20260710001938-2d4ebafec5c5

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.5 · CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-71543: 0.42% estimated exploitation activity in the next 30 days; percentile 36.51 (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 ACL Policies OpenBao supports "templated polices": Policies with placeholders that are replaced at evaluation time. This allows you to write a single policy which e.g. grants user "alice" access to all entries in a key value engine prefixed with alice/ while granting "bob" access to bob/, "carol" access to carol/, etc. If the data used in the template can be controlled by an attacker (e.g. your system allows the user to freely select their username) and "globbing" characters are considered valid ( e.g. is a valid username) they will be able to escalate their privileges. The problematic characters are , + and /. PKI Secrets Engine allowedurisanstemplate and alloweddomains Polices The PKI secrets engine allows you to limit the "common names" a user can requests a TLS certificate for. Similar to the ACL polices this allows you to restrict e.g. "alice" to alice.example.com, "bob" to bob.example.com, etc. via templates. Again, if an attacker can control this data freely, they can…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-59w7-v8rr-pr4p

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6556

  4. Revision 1 · created ·

    Published from osv record GHSA-59w7-v8rr-pr4p

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-71543

Advisory: OpenBao's Templated Policies Allow Privilege Escalation via Wildcard Characters
IDs: CVE-2026-71543, GHSA-59w7-v8rr-pr4p
Record: https://patchnext.com/advisories/cve-2026-71543 (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: High (CVSS 7.5)
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-20260710001938-2d4ebafec5c5. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/openbao/openbao: affected < 0.0.0-20260710001938-2d4ebafec5c5; >= 0.1.0, <= 1.1.5; fixed in 0.0.0-20260710001938-2d4ebafec5c5

## 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/GHSA-59w7-v8rr-pr4p (OSV record GHSA-59w7-v8rr-pr4p lists affected ranges: Go github.com/openbao/openbao >=0 =0.1.0 <=1.1.5)
- Verified: https://osv.dev/vulnerability/GO-2026-6556 (OSV record GO-2026-6556 lists affected ranges: Go github.com/openbao/openbao >=0 =0.1.0)
- Verified: https://github.com/advisories/GHSA-59w7-v8rr-pr4p (GitHub-reviewed advisory GHSA-59w7-v8rr-pr4p 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…