OpenBao: LDAPi ldaputil (wrong escape func)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.8 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2026-55770: 0.53% estimated exploitation activity in the next 30 days; percentile 44.59 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

1. Description Component sdk/helper/ldaputil/client.go — the shared LDAP utility library used by both the LDAP authentication backend and OpenLDAP secrets engine to construct LDAP search filters and bind DNs. Root Cause The LDAP utility contains a function selection error that causes incorrect escaping of user-controlled input in LDAP filter construction. Two lines construct the bindDN using EscapeLDAPValue(): The problem: EscapeLDAPValue() implements RFC 4514 escaping, which is designed for Distinguished Name (DN) components. It only escapes characters meaningful in DNs: +, ,, ;, ", \, <, , and leading/trailing spaces. LDAP search filters (RFC 4515) have a different set of special characters: , (, ), \, and NUL (\x00). None of these are escaped by EscapeLDAPValue(). The correct function is ldap.EscapeFilter() from the github.com/go-ldap/ldap/v3 package. The irony: the same file uses ldap.EscapeFilter() correctly at lines 225-226 in RenderUserSearchFilter() for the UserFilter…

Published by the source

19 Jun 2026, 21:42 UTC

Last modified by the source

19 Jun 2026, 21:42 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6mwx-4547-5vc9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-55770

Advisory: OpenBao: LDAPi ldaputil (wrong escape func)
IDs: CVE-2026-55770, GHSA-6mwx-4547-5vc9
Record: https://patchnext.com/advisories/cve-2026-55770 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
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-20260617104213-10b7825c714c. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/openbao/openbao: affected >= 0.1.0, <= 2.5.4; < 0.0.0-20260617104213-10b7825c714c; fixed in 0.0.0-20260617104213-10b7825c714c

## 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://github.com/advisories/GHSA-6mwx-4547-5vc9 (GitHub-reviewed advisory GHSA-6mwx-4547-5vc9 lists affected ranges: Go github.com/openbao/openbao >=0.1.0 =0 <0.0.0-20260617104213-10b7825c714c)

Commands are suggestions: review each one before running it.