CVE-2026-47138: Parse Server Denial of Service Vulnerability
HIGHCVE-2026-47138 is a HIGH denial of service vulnerability (CWE-1333: Inefficient Regular Expression Complexity) affecting Parse Server libraries in the npm ecosystem. The issue involves pre-authentication denial of service via client version header regex backtracking. Remediation is available by upgrading affected packages to version 9.9.1-alpha.1, 8.6.77.
CVE-2026-47138 at a Glance
How to Fix CVE-2026-47138
To remediate this vulnerability, upgrade all affected Parse Server dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install parse-server@9.9.1-alpha.1
npm install parse-server@8.6.77
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls parse-server
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-47138, inspect your project dependencies using npm:
npm ls parse-server
Analyze the terminal output to locate any version of Parse Server in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 9.9.1-alpha.1), your application is affected.
Note: The npm ls parse-server command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-1333: Inefficient Regular Expression Complexity, where the product uses a regular expression with a worst-case computational complexity that is inefficient and possibly exponential. In Parse Server, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-47138 Affected Parse Server Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
parse-server
|
npm |
≥ 9.0.0
< 9.9.1-alpha.1
|
9.9.1-alpha.1
|
|
parse-server
|
npm |
< 8.6.77
|
8.6.77
|
References
Frequently Asked Questions
What is CVE-2026-47138?
Which Parse Server versions are affected?
What version fixes CVE-2026-47138?
Is parse-server affected?
What CWE is associated with CVE-2026-47138?
How can I check npm dependencies for CVE-2026-47138?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-38m6-82c8-4xfm",
"modified" : "2026-06-12T21:59:40Z",
"published" : "2026-05-23T00:11:25Z",
"aliases" : [ "CVE-2026-47138" ],
"summary" : "Parse Server: Pre-authentication denial of service via client version header regex backtracking",
"details" : "### Impact\n\nAn 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.\n\n### Patches\n\nThe client SDK version capture and parsing have been removed entirely. The Parse JS SDK compatibility table defines a strict version-pinned contract between Parse Server and the Parse JS SDK; server-side adaptation to client SDK version is an obsolete pattern that contradicts that contract. The vulnerable parser, the `clientSDK` parameter that threaded its output through routers, and the legacy code path it gated are all removed. The `X-Parse-Client-Version` header and `_ClientVersion` JSON body field are now silently ignored on every request; supported Parse SDKs are unaffected.\n\n### Workarounds\n\nDeploy 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. A header-size cap alone is insufficient: the body-field variant requires inspection of JSON content. Upgrading to the patched version is the recommended remediation.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "parse-server"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "9.0.0"
}, {
"fixed" : "9.9.1-alpha.1"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "parse-server"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "8.6.77"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/parse-community/parse-server/security/advisories/GHSA-38m6-82c8-4xfm"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-47138"
}, {
"type" : "WEB",
"url" : "https://github.com/parse-community/parse-server/pull/10463"
}, {
"type" : "WEB",
"url" : "https://github.com/parse-community/parse-server/pull/10464"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/parse-community/parse-server"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-1333" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-05-23T00:11:25Z",
"nvd_published_at" : "2026-06-12T19:16:28Z"
}
}