Authentication Bypass in Parse Server (CVE-2026-87806)
Summary
Authentication bypass in Parse Server (CVE-2026-87806). Confidential information can be exposed externally. Mitigation: upgrade to 8.6.88 or later.
Original description
The description as published by the source.
Parse Server versions <= 8.6.87 and >= 9.0.0 < 9.10.1 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, which require the password to be a non-empty string and reject the request before contacting the directory.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-87806 has been found in Parse Server.
Confidential information can be exposed externally. CVSS score: 7.4/10.
What to do: upgrade Parse Server to 8.6.88 or later.
If unsure, ask your IT team or search "Parse Server CVE-2026-87806" on the vendor's site.
CVE-2026-87806 (Parse Server) — CWE-287 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 8.6.88 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Authentication bypass (CWE-287) exists in Parse Server.
Check the vendor advisory for the affected versions of Parse Server.
Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.
Update to 8.6.88.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Parse Server を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Parse Server to 8.6.88ステージング環境で 8.6.88 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web vulncheck.com
- web nvd.nist.gov
- web github.com