/

CVE-2026-87806

Severity:

HIGH RISK

(7.4)

Authentication Bypass (CWE-287) in Parse Server LDAP

CVE-2026-87806

Deferred

Vulnerability type

Category:

Authentication Bypass

CWE:

CWE-287

Impact:

Account Takeover

Severity:

HIGH RISK

(7.4)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Parse Server's built-in LDAP authentication adapter can accept an empty password and treat a successful directory response as proof of authentication. When the configured directory permits unauthenticated LDAP simple binds, an attacker who knows a directory username may obtain a valid session for that account and potentially take it over.

Affected context

The issue occurs only in Parse Server deployments that enable the built-in LDAP authentication adapter. Exploitability depends on the connected directory's behavior: directories that accept zero-length LDAP credentials and return success for anonymous binds may be affected, while directories configured to reject unauthenticated simple binds may not be exploitable.

Exploit preconditions

  • Attack surface: The Parse Server LDAP authentication endpoint
  • Required access: No valid account credentials are required, but the attacker must know a directory username
  • Trigger point: LDAP authentication when the supplied password is empty or absent
  • Why exploitation is possible: The adapter contacts the directory without first requiring a non-empty password and interprets a non-error response as successful authentication
  • Environmental dependency: The configured LDAP directory must permit unauthenticated simple binds or otherwise return success for the empty credential

Why this happens

The adapter failed to enforce a basic credential precondition before initiating LDAP authentication. It forwarded an empty client-supplied password to the directory and treated any non-error response as proof that the user had authenticated. This maps to CWE-287: Improper Authentication, because the application accepted a directory response that represented anonymous access rather than verification of the claimed user's password.

Potential impact

  • An attacker may obtain a valid session token for a known directory username
  • User accounts could be taken over without knowledge of their passwords
  • Attackers could access data and operations permitted to the impersonated account
  • Administrative or privileged accounts could be exposed if their usernames are discoverable
  • Audit records could incorrectly attribute attacker activity to legitimate users

General mitigation guidance

Mitigation generally focuses on enforcing authentication requirements before contacting the directory and reducing trust in ambiguous directory responses.

Defensive patterns include:

  • Require the password to be present, a string, and non-empty before attempting LDAP authentication
  • Reject empty-credential requests at the application boundary
  • Treat anonymous or unauthenticated LDAP bind results as authentication failure
  • Configure directories to refuse unauthenticated simple binds where operationally appropriate
  • Apply least privilege to LDAP-bound application accounts and Parse Server users
  • Use explicit authentication policies that distinguish anonymous access from verified identity

How teams detect issues like this

Detection can combine application, directory, and source-code review signals:

  • Review authentication code for missing, empty, or type-ambiguous credential validation
  • Use static analysis and code review rules that flag authentication decisions based solely on non-error responses
  • Monitor LDAP logs for successful anonymous or zero-length simple binds associated with application authentication flows
  • Alert on session issuance following requests with missing or empty password fields
  • Enforce security policies requiring explicit credential validation and denial of anonymous authentication in CI and deployment checks

Sources

SourceLink
github.comgithub.com/parse-community/parse-server/security/advisories/GHSA-863r-39r9-vfcf
vulncheck.comvulncheck.com/advisories/parse-server-9.0.0-authentication-bypass-via-ldap-empty-password

Frequently asked

questions

It can be exploitable through the Parse Server authentication interface when LDAP authentication is enabled and the connected directory accepts unauthenticated simple binds.

The attacker generally does not need valid credentials, but must know a directory username that can be submitted to the LDAP authentication adapter.

Require a non-empty password before contacting the directory, and accept authentication only after a response that clearly verifies the user's credentials rather than merely indicating that no LDAP error occurred.

Validate credential presence and type at the application boundary, disable or reject anonymous directory authentication where appropriate, and monitor for successful sessions created from empty-credential requests.

Find out what's already
exploitable in your codebase.