Answer in brief
CVE-2026-55770 records a Medium severity vulnerability in OpenBao: LDAPi ldaputil (wrong escape func). The current sources do not mark it as known exploited. The current feed maps openbao/openbao (generic), github.com/openbao/openbao (go), github.com/openbao/openbao (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps openbao/openbao (generic), github.com/openbao/openbao (go), github.com/openbao/openbao (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| openbao/openbaogeneric | < 2.5.5 | Not reported |
| github.com/openbao/openbaogo | >=0.1.0,<=2.5.4 | Not reported |
| github.com/openbao/openbaogo | <0.0.0-20260617104213-10b7825c714c | 0.0.0-20260617104213-10b7825c714c |
Published upstream
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
OpenBao is an open source identity-based secrets management system. Prior to 2.5.5, OpenBao used EscapeLDAPValue, an RFC 4514 distinguished-name escaping function, where RFC 4515 LDAP search-filter escaping was required in sdk/helper/ldaputil/client.go GetUserDN. With the LDAP authentication backend configured for an Active Directory UPNDomain path or UserDN and UserAttr binding, an attacker-controlled username containing filter metacharacters could alter the search predicate and select a different directory entry because EscapeLDAPValue does not neutralize the characters handled by ldap.EscapeFilter. A resulting token could be associated with another LDAP identity and gain access to secrets, policies, or modification capabilities assigned to that identity. This issue is fixed in version 2.5.5.
Quoted source text, attributed separately from HOL analysis.