CVE-2026-87806

Parse Server 9.0.0 Authentication Bypass via LDAP Empty Password

HIGH
7.4
CVSS Score
Published: September 9, 2026 at 11:20 AM UTC
Updated: September 10, 2026 at 08:18 PM UTC
2 products affected across 2 vendorsParse ServerParse Server

Using parse-server by parse-community?

Get instant alerts when new vulnerabilities affect parse-server - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.4
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 8.6.889.0.0 ≤ v < 9.10.1-alpha.7
Affected range stops below 8.6.88, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.10.1-alpha.7, so it looks safe — our inference, not a vendor statement
v < 8.6.889.0.0 ≤ v < 9.10.1-alpha.79.0.0
Vendor states this is fixed in 8.6.88 (unaffected)
Vendor states this is fixed in 9.10.1-alpha.7 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.4HIGHVulnCheck
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-287

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card