OpenBao LDAP MFA Enforcement Bypass When Using Username As Alias (CVE-2025-55001)
OpenBao versions 2.3.1 and below contain a vulnerability where the LDAP authentication method's username_as_alias=true parameter allows bypassing of alias-specific MFA enforcement. This occurs because the username is used verbatim without normalization, enabling attackers to circumvent MFA policies tied to entity aliases. The issue is fixed in version 2.3.2 by removing this parameter and updating aliases accordingly.
AI Analysis
Technical Summary
OpenBao, a software solution for managing sensitive data, had a vulnerability (CVE-2025-55001) in versions up to 2.3.1 where MFA enforcement based on entity aliases could be bypassed when using the LDAP authentication method with the username_as_alias=true parameter. The vulnerability arises because the caller-supplied username is used without normalization, allowing attackers to bypass alias-specific MFA requirements. The vulnerability was addressed in version 2.3.2 by removing the usage of username_as_alias=true and updating entity aliases.
Potential Impact
Attackers can bypass multi-factor authentication enforcement policies that rely on entity aliases in OpenBao when the LDAP authentication method is configured with username_as_alias=true. This could reduce the effectiveness of MFA protections, potentially allowing unauthorized access to sensitive data managed by OpenBao.
Mitigation Recommendations
A patch is available in OpenBao version 2.3.2 that fixes this vulnerability. Users should upgrade to version 2.3.2 or later. As a workaround, remove all usage of the username_as_alias=true parameter in the LDAP authentication method and update any entity aliases accordingly.
OpenBao LDAP MFA Enforcement Bypass When Using Username As Alias (CVE-2025-55001)
Description
OpenBao versions 2.3.1 and below contain a vulnerability where the LDAP authentication method's username_as_alias=true parameter allows bypassing of alias-specific MFA enforcement. This occurs because the username is used verbatim without normalization, enabling attackers to circumvent MFA policies tied to entity aliases. The issue is fixed in version 2.3.2 by removing this parameter and updating aliases accordingly.
Affected software
pkg:bitnami/openbaoRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
OpenBao, a software solution for managing sensitive data, had a vulnerability (CVE-2025-55001) in versions up to 2.3.1 where MFA enforcement based on entity aliases could be bypassed when using the LDAP authentication method with the username_as_alias=true parameter. The vulnerability arises because the caller-supplied username is used without normalization, allowing attackers to bypass alias-specific MFA requirements. The vulnerability was addressed in version 2.3.2 by removing the usage of username_as_alias=true and updating entity aliases.
Potential Impact
Attackers can bypass multi-factor authentication enforcement policies that rely on entity aliases in OpenBao when the LDAP authentication method is configured with username_as_alias=true. This could reduce the effectiveness of MFA protections, potentially allowing unauthorized access to sensitive data managed by OpenBao.
Mitigation Recommendations
A patch is available in OpenBao version 2.3.2 that fixes this vulnerability. Users should upgrade to version 2.3.2 or later. As a workaround, remove all usage of the username_as_alias=true parameter in the LDAP authentication method and update any entity aliases accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- BIT-openbao-2025-55001
- Osv Schema Version
- 1.6.2
- Aliases
- ["CVE-2025-55001"]
- Ecosystems
- ["Bitnami"]
- Database Specific Severity
- Medium
- Cvss Version
- null
Patch Information
Threat ID: 6aa005f6acd9273b49ab63bd
Added to database: 09/08/2026, 12:56:22 UTC
Last enriched: 09/08/2026, 13:32:43 UTC
Last updated: 09/08/2026, 13:32:43 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.