CVE-2026-34573: parse-server has GraphQL complexity validator exponential fragment traversal DoS
Impact The GraphQL query complexity validator can be exploited to cause a denial-of-service by sending a crafted query with binary fan-out fragment spreads. A single unauthenticated request can block the Node.js event loop for seconds, denying service to all concurrent users. This only affects deployments that have enabled the requestComplexity.graphQLDepth or requestComplexity.graphQLFields configuration options.
Published Mar 31, 2026
Affected packages
parse-server
- Ecosystem
- npm
- Affected
- >= 9.0.0, < 9.7.0-alpha.12
- Fixed in
- 9.7.0-alpha.12
- Check
npm ls parse-server
parse-server
- Ecosystem
- npm
- Affected
- < 8.6.68
- Fixed in
- 8.6.68
- Check
npm ls parse-server
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
The GraphQL query complexity validator can be exploited to cause a denial-of-service by sending a crafted query with binary fan-out fragment spreads. A single unauthenticated request can block the Node.js event loop for seconds, denying service to all concurrent users. This only affects deployments that have enabled the requestComplexity.graphQLDepth or requestComplexity.graphQLFields configuration options.
Patches
The fix replaces the per-branch fragment traversal with memoized fragment computation, reducing the traversal from exponential O(2^N) to linear O(N) time. Additionally, early termination aborts the traversal as soon as configured limits are exceeded.
Workarounds
Disable GraphQL complexity limits by setting requestComplexity.graphQLDepth and requestComplexity.graphQLFields to -1 (the default).
Resources
- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-mfj6-6p54-m98c
- Fix Parse Server 9: https://github.com/parse-community/parse-server/pull/10344
- Fix Parse Server 8: https://github.com/parse-community/parse-server/pull/10345
Credited to bugbunny-research, mtrezza.
References
- https://github.com/parse-community/parse-server/security/advisories/GHSA-mfj6-6p54-m98c
- https://nvd.nist.gov/vuln/detail/CVE-2026-34573
- https://github.com/parse-community/parse-server/pull/10344
- https://github.com/parse-community/parse-server/pull/10345
- https://github.com/parse-community/parse-server/commit/ea15412795f34594cc8a674fe858d445675e0295
- https://github.com/parse-community/parse-server/commit/f759bda075298ec44e2b4fb57659a0c56620483b
- https://github.com/advisories/GHSA-mfj6-6p54-m98c
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
