External risk intelligence

Parse Server LDAP Authentication Bypass via Empty Password

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-87806

Parse Server is frequently deployed as an internet-facing API, making services using the LDAP authentication adapter highly reachable. Because this vulnerability allows authentication bypass via zero-length credentials, any instance exposing this configuration to the public internet is at direct risk of exploitation.

Authentication Bypass

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

Parse Server, when using its built-in LDAP authentication, has a critical vulnerability that can allow unauthorized access to accounts. This issue arises because the system may not properly verify credentials, potentially enabling attackers to gain session tokens for known user accounts. The primary concern is confirming if your environment utilizes this specific LDAP adapter configuration, as only those deployments are susceptible.

  • Bypass of account login controls.
  • Critical for confirming if your configuration is at risk.
  • Assess relevance to understand potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by targeting Parse Server deployments that use the LDAP authentication adapter. If the adapter is configured to forward client-supplied passwords to the directory without proper validation, an attacker can send a request with an empty password for a known user. Certain directory configurations, like a default Active Directory setup, will treat this as a valid, anonymous bind, allowing the attacker to receive a session token for that user and take over the account.

  • Entry condition: LDAP adapter enabled; user's username known.
  • Trigger point: Empty password sent during LDAP simple bind.
  • Resulting risk: Unauthenticated account takeover.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to gain access to user accounts by exploiting a flaw in the LDAP authentication adapter. When an attacker knows a valid directory username, they can bypass authentication by supplying an empty password. This allows the attacker to obtain a valid session token, potentially leading to account takeover, but only when the LDAP adapter is enabled and configured in a specific way where the directory responds to unauthenticated simple binds.

  • User account credentials and session tokens.
  • Empty password bypass to LDAP server.
  • Unauthorized account access and takeover.

Operational Fix

Recommended remediation, mitigation, and detection steps

Attackers can bypass authentication in Parse Server's LDAP adapter by sending an empty password, leading to account takeover. This affects deployments that enable the LDAP adapter and are configured to accept unauthenticated simple binds. The first step is to identify all Parse Server instances, determine if the LDAP adapter is enabled and exposed, and confirm the accountable owner for remediation.

  • Assign ownership to application or platform teams.
  • Verify LDAP adapter configuration and reachability.
  • Plan coordinated remediation or vendor engagement.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Parse Server?

Parse Server is an open-source backend framework commonly used to host mobile and web application data. It provides built-in services like database management, user authentication, and file storage. By using adapters, it can connect to external systems—such as LDAP directories—to manage user login processes within a customized application infrastructure.

What does CWE-287 mean for CVE-2026-87806?

CWE-287 refers to Improper Authentication. In this case, the Parse Server LDAP adapter fails to verify that a password was actually provided. By accepting a zero-length credential, the server incorrectly treats an empty input as a successful authentication request, which leads to the system granting a session token to the user without valid proof of identity.

How can an attacker trigger this vulnerability?

An attacker needs to identify a username on the directory service and send an authentication request with an empty password. If the underlying directory is configured to allow unauthenticated binds, it will mistakenly grant access. This flaw does not trigger if the directory rejects unauthenticated simple binds, such as with a standard OpenLDAP setup, or if the LDAP adapter is not enabled in the application.

Is my deployment at risk according to Halo Surface Signal?

Halo Surface Signal identifies that Parse Server is frequently deployed as an internet-facing API, which increases risk. Because this vulnerability allows authentication bypass, any instance using the LDAP adapter that is reachable from the public internet is at direct risk. If your service is internal-only, the potential for unauthorized access is lower but should still be assessed.

What should I do first to address this?

Start by auditing your Parse Server instances to determine if the LDAP authentication adapter is active. Confirm whether your directory service accepts unauthenticated simple binds, as this is a requirement for the vulnerability to be exploitable. Once you identify impacted instances, prioritize upgrading to the patched versions—8.6.88 or 9.10.1-alpha.7—to enforce mandatory password validation.

References