Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-87806 – Authentication Bypass / Account Takeover – Parse Server LDAP Adapter (< 8.6.88, 9.0

Be the first to know when new zero-days emerge:

Summary

CVE-2026-87806 is an authentication bypass vulnerability (CWE-287: Improper Authentication) in the built-in LDAP authentication adapter of Parse Server. Deployments that enable the LDAP adapter can be bypassed by an unauthenticated attacker who supplies a known username with an empty password, allowing account takeover. The issue carries a CVSS score of 9.1 (Critical).

Technical details

  • Root cause: the LDAP adapter forwarded the client-supplied password directly to the directory server without verifying that a password had actually been supplied.
  • The adapter treated any non-error response from the directory as proof of successful authentication.
  • A zero-length credential turns an LDAP simple bind into the "unauthenticated authentication mechanism" described in RFC 4513 §5.1.2, which some directory services — including Active Directory in its default configuration — answer with success and map to an anonymous session.
  • Attack vector: Network, no privileges or user interaction required; the attacker only needs to know a valid directory username.
  • Impact: an unauthenticated attacker can obtain a valid session token for the targeted account, resulting in account takeover. Confidentiality and integrity impacts are high; availability is not affected.
  • Exploitability is conditional: only Parse Server deployments that have the LDAP authentication adapter enabled and connect to a directory that accepts unauthenticated binds (e.g., default Active Directory) are exploitable. Directories that reject unauthenticated simple binds (e.g., stock OpenLDAP) are not affected.

Affected software

  • Parse Server versions 0 through 8.6.87
  • Parse Server versions 9.0.0 through 9.10.1-alpha.6

Severity

  • CVSS 4.0 Base Score: 9.1 (Critical) — CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
  • CVSS 3.1 Base Score: 7.4 (High) — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade to Parse Server 8.6.88 or later (for the 8.x line), or 9.10.1-alpha.7 or later (for the 9.x line), which correct the LDAP adapter’s handling of empty passwords.
  • If patching is not immediately possible: disable the LDAP authentication adapter until the upgrade can be applied, or ensure the connected directory server is configured to reject unauthenticated/anonymous simple binds (RFC 4513 unauthenticated bind mechanism), which prevents the empty-password bypass from succeeding.
  • Review authentication logs for anonymous or unexpectedly successful LDAP bind events as a precaution.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • access-control-expose-headers response header: X-Parse-Job-Status-Id
  • access-control-allow-headers response header: X-Parse-Master-Key, X-Parse-REST-API-Key, X-Parse-Javascript-Key

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge