CVE-2026-30946: Parse Server affected by denial-of-service via unbounded query complexity in REST and GraphQL API
Impact An unauthenticated attacker can exhaust Parse Server resources (CPU, memory, database connections) through crafted queries that exploit the lack of complexity limits in the REST and GraphQL APIs. All Parse Server deployments using the REST or GraphQL API are affected.
Published Mar 11, 2026 · Updated Mar 16, 2026
Affected packages
parse-server
- Ecosystem
- npm
- Affected
- < 8.6.15
- Fixed in
- 8.6.15
- Check
npm ls parse-server
parse-server
- Ecosystem
- npm
- Affected
- >= 9.0.0, < 9.5.2-alpha.2
- Fixed in
- 9.5.2-alpha.2
- Check
npm ls parse-server
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
An unauthenticated attacker can exhaust Parse Server resources (CPU, memory, database connections) through crafted queries that exploit the lack of complexity limits in the REST and GraphQL APIs.
All Parse Server deployments using the REST or GraphQL API are affected.
Patches
The vulnerability is fixed by introducing configurable request complexity limits via the requestComplexity server option with the following keys:
subqueryDepth: Maximum nesting depth for$inQuery,$notInQuery,$select,$dontSelectincludeDepth: Maximum depth of dot-separatedincludepathsincludeCount: Maximum number ofincludefields per querygraphQLDepth: Maximum depth of GraphQL field selectionsgraphQLFields: Maximum number of field selections in a GraphQL query
Requests using master key or maintenance key bypass these limits. Set any property to -1 to disable that specific limit.
In versions 8.6.15 and 9.5.2-alpha.2, these limits were enabled by default. This unintentionally introduced a breaking change for some applications with legitimate complex queries. In versions 8.6.46 and 9.6.0-alpha.22, the defaults were changed to -1 (disabled) to restore backwards compatibility.
The limits remain available as configuration options. To mitigate the vulnerability, upgrade to a patched version and set each requestComplexity property to a value appropriate for your application.
Workarounds
There is no known workaround.
References
- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-cmj3-wx7h-ffvg
- Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.2-alpha.2
- Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.15
Credited to mtrezza.
References
- https://github.com/parse-community/parse-server/security/advisories/GHSA-cmj3-wx7h-ffvg
- https://nvd.nist.gov/vuln/detail/CVE-2026-30946
- https://github.com/parse-community/parse-server/releases/tag/8.6.15
- https://github.com/parse-community/parse-server/releases/tag/9.5.2-alpha.2
- https://github.com/advisories/GHSA-cmj3-wx7h-ffvg
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-61448
Parse Server vulnerable to stored XSS via malformed Content-Type bypassing file upload extension blocklist
low2.1Oct 29, 2026CVE-2026-50008
parse-server: Server option routeAllowList is bypassable through batch sub-requests
medium6.9Jun 19, 2026CVE-2026-53724
parse-server: Stored XSS via trailing-dot filename bypassing file upload extension blocklist
low2.1Jun 19, 2026CVE-2026-53725
parse-server: Endpoints `/login` and `/verifyPassword` disclose MFA secrets and protected fields when `_User` get is denied
medium5.9Jun 19, 2026CVE-2026-53726
parse-server: Relation `$relatedTo` query bypasses `protectedFields` and owning-object ACL
medium6.9Jun 19, 2026CVE-2026-55778
parse-server: Stored XSS via non-standard file extension bypassing file upload extension blocklist
low2.1Jun 19, 2026
