Vulnerability in parse-server (CVE-2026-47138)
Summary
Vulnerability in parse-server (CVE-2026-47138). Risk of unauthorized operations or information disclosure. Exploitable via clientSDK. Mitigation: upgrade to 8.6.77 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. Prior to versions 8.6.77 and 9.9.1-alpha.1, an unauthenticated attacker who knows a publicly-known Parse Application ID can submit a single HTTP request whose client SDK version field contains adversarial input that triggers polynomial backtracking in a request-header parser. The parsing runs before session authentication and before rate limiting on every /parse/* request, so the request consumes seconds to minutes of synchronous CPU on a Node.js worker before any access control evaluates it. A small number of concurrent requests can saturate a worker; a single large request via the body-field variant can pin a worker for minutes. Production deployments running the default configuration are affected. This issue has been patched in versions 8.6.77 and 9.9.1-alpha.1.
Source: GitHub Security Advisories (Global) 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-47138 has been found in parse-server.
Attackers can target a specific entry point like clientSDK over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade parse-server to 8.6.77 or later.
If unsure, ask your IT team or search "parse-server CVE-2026-47138" on the vendor's site.
CVE-2026-47138 (parse-server) — CWE-1333
Attack surface: clientSDK / _ClientVersion
Patched: 8.6.77 — apply immediately
Workaround: Deploy a reverse proxy or WAF in front of Parse Server that strips or strictly size-limits the X-Parse-Client-Version header AND the _ClientVersion field in JSON request bodies on every /parse/* route before forwarding to the server.
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.
A vulnerability (CWE-1333) exists in parse-server. Attackers reach the vulnerable code path via clientSDK.
Check the vendor advisory for the affected versions of parse-server. Attack surface: clientSDK / _ClientVersion.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 8.6.77.
Workaround: Deploy a reverse proxy or WAF in front of Parse Server that strips or strictly size-limits the X-Parse-Client-Version header AND the _ClientVersion field in JSON request bodies on every /parse/* route before forwarding to the server.
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 temporary workaround mitigate
Deploy a reverse proxy or WAF in front of Parse Server that strips or strictly size-limits the `X-Parse-Client-Version` header AND the `_ClientVersion` field in JSON request bodies on every `/parse/*` route before forwarding to the server.パッチが適用されるまでの応急処置として、Deploy a reverse proxy or WAF in front of Parse Server that strips or strictly size-limits the
X-Parse-Client-Versionheader AND the_ClientVersionfield in JSON request bodies on every/parse/*route before forwarding to the server. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade parse-server to 8.6.77ステージング環境で 8.6.77 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-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
- patch github.com
- web github.com