CVE-2026-87806: Parse Server 9.0.0 Authentication Bypass via LDAP Empty Password
Parse Server versions <= 8.6.87 and >= 9.0.0 < 9.10.1-alpha.7 contain an authentication bypass in the built-in LDAP authentication adapter. The adapter forwarded the client-supplied password to the directory without verifying that a password had been supplied, and treated any non-error response from the directory as proof of authentication. A zero-length credential turns an LDAP simple bind into the unauthenticated authentication mechanism described in RFC 4513 section 5.1.2, which some directories (including Active Directory in its default configuration) answer with success while mapping the connection to anonymous. As a result, an unauthenticated attacker who knows a directory username can obtain a valid session token for that account, resulting in account takeover. Only deployments that enable the LDAP authentication adapter are affected, and deployments whose directory refuses unauthenticated simple bind (such as a stock OpenLDAP configuration) are not exploitable. The issue is fixed in 8.6.88 and 9.10.1-alpha.7, which require the password to be a non-empty string and reject the request before contacting the directory.
Security readout for executives and security teams
Plain-English summary
Parse Server’s optional LDAP login can let an attacker take over a directory-linked account using a known username and an empty password. The flaw matters only when LDAP authentication is enabled and the connected directory accepts unauthenticated simple binds. Successful abuse yields a valid session token for the targeted account.
Executive priority
Treat remediation as immediate for LDAP-enabled deployments, especially those connected to Active Directory. Account takeover could expose or alter data accessible to the impersonated user. Systems without the LDAP adapter, or with directories that reject unauthenticated binds, are not exploitable through this flaw but should still be documented and verified.
Technical view
Affected versions forward a zero-length password to LDAP without first requiring a non-empty credential. Under RFC 4513, this becomes an unauthenticated simple bind. If the directory returns success, the adapter incorrectly treats that response as authenticated and issues a session token. Versions 8.6.88 and 9.10.1-alpha.7 add local password validation.
Likely exposure
Exposure is limited to Parse Server versions through 8.6.87 or from 9.0.0 before 9.10.1-alpha.7 that enable the built-in LDAP adapter. Exploitation additionally requires a directory accepting unauthenticated simple binds. The bundle identifies default Active Directory configurations as potentially susceptible and stock OpenLDAP configurations as refusing this bind.
Exploitation context
No active exploitation is established by the supplied sources, and the CVE is not identified as being in KEV. Abuse requires knowledge of a directory username, LDAP authentication being enabled, and a directory response that reports success for an unauthenticated simple bind. No prior account access or user interaction is required.
Researcher notes
The security boundary failure combines missing input validation with incorrect interpretation of LDAP success. Directory behavior is the decisive environmental condition. Assessment should distinguish LDAP adapter enablement, Parse Server branch, exact version, and directory unauthenticated-bind policy. The supplied evidence does not establish public exploitation or observed attacks.
Mitigation direction
Upgrade 8.x deployments to version 8.6.88 or later.
Upgrade 9.x deployments to 9.10.1-alpha.7 or a later vendor-fixed release.
If upgrading is delayed, disable the LDAP authentication adapter.
Configure the directory to reject unauthenticated simple binds as defense in depth.
Check current vendor guidance before selecting later release versions.
Validation and detection
Inventory Parse Server versions and identify deployments using the built-in LDAP authentication adapter.
Confirm each LDAP-enabled deployment runs the appropriate fixed version or later.
Verify the connected directory rejects unauthenticated simple binds.
Validate empty-password authentication is rejected in an authorized test environment after remediation.
Review Parse Server and directory logs for unexpected anonymous binds or suspicious account sessions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-287 · source CWE mapping
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.