Authorization Flaw in parse-server (CVE-2026-50008)
Summary
Vulnerability in parse-server (CVE-2026-50008). Risk of unauthorized operations or information disclosure. Exploitable via routeAllowList. Mitigation: upgrade to 9.9.1-alpha.3 or later.
Original description
The description as published by the source.
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. From version 9.8.0 to before version 9.9.1-alpha.3, the routeAllowList server option restricts external client access to a configured list of REST API routes. The check is only enforced as Express middleware against the outer HTTP request URL, so the /batch handler dispatches each sub-request to the internal router without re-running the allow-list check. An external caller whose outer route matches batch can issue batch sub-requests to any REST API route that the operator omitted from the allow-list. Authentication, ACL, CLP, and other inner-route authorization controls still apply — only the operator-configured route firewall is bypassed. This issue has been patched in version 9.9.1-alpha.3.
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-50008 has been found in parse-server.
Attackers can target a specific entry point like routeAllowList over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade parse-server to 9.9.1-alpha.3 or later.
If unsure, ask your IT team or search "parse-server CVE-2026-50008" on the vendor's site.
CVE-2026-50008 (parse-server) — CWE-863
Attack surface: routeAllowList / batch
Patched: 9.9.1-alpha.3 — 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.
Incorrect authorization (CWE-863) exists in parse-server. Attackers reach the vulnerable code path via routeAllowList.
Check the vendor advisory for the affected versions of parse-server. Attack surface: routeAllowList / batch.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 9.9.1-alpha.3.
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. Run grep -r 'parse-server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'parse-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
parse-serverを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade parse-server to 9.9.1-alpha.3ステージング環境で 9.9.1-alpha.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com