CVE-2026-34573: Parse Server: GraphQL complexity validator exponential fragment traversal DoS

Published Mar 31, 2026
·
Updated

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

Other sources

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.68 and 9.7.0-alpha.12, 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. This issue has been patched in versions 8.6.68 and 9.7.0-alpha.12.

MITRE

Affected Software

16 affected componentsFixes available
npm/parse-server<8.6.68, <9.7.0-alpha.12
npm/parse-server<8.6.68
8.6.68
npm/parse-server>=9.0.0<9.7.0-alpha.12
9.7.0-alpha.12
parseplatform Parse-server Node.js<8.6.68
parseplatform Parse-server Node.js>=9.0.0<9.7.0
parseplatform Parse-server Node.js=9.7.0-alpha1
parseplatform Parse-server Node.js=9.7.0-alpha10
parseplatform Parse-server Node.js=9.7.0-alpha11
parseplatform Parse-server Node.js=9.7.0-alpha2
parseplatform Parse-server Node.js=9.7.0-alpha3
parseplatform Parse-server Node.js=9.7.0-alpha4
parseplatform Parse-server Node.js=9.7.0-alpha5
parseplatform Parse-server Node.js=9.7.0-alpha6
parseplatform Parse-server Node.js=9.7.0-alpha7
parseplatform Parse-server Node.js=9.7.0-alpha8
parseplatform Parse-server Node.js=9.7.0-alpha9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/parse-server to a version that resolves this vulnerability.

    Fixed in 8.6.68
  2. Upgrade

    Upgrade npm/parse-server to a version that resolves this vulnerability.

    Fixed in 9.7.0-alpha.12
  3. Upgrade

    Upgrade parse-server to a version that resolves this vulnerability.

    Fixed in 8.6.68
  4. Upgrade

    Upgrade parse-server to a version that resolves this vulnerability.

    Fixed in 9.7.0-alpha.12
  5. Configuration

    Disable GraphQL complexity limits by setting requestComplexity.graphQLDepth to -1 (the default). This workaround is relevant when requestComplexity.graphQLDepth/requestComplexity.graphQLFields are enabled.

    Parse Server (GraphQL complexity validator) requestComplexity.graphQLDepth = -1
  6. Configuration

    Disable GraphQL complexity limits by setting requestComplexity.graphQLFields to -1 (the default). This workaround is relevant when requestComplexity.graphQLDepth/requestComplexity.graphQLFields are enabled.

    Parse Server (GraphQL complexity validator) requestComplexity.graphQLFields = -1

Event History

Mar 31, 2026
CVE Published
via MITRE·03:06 PM
Data Sourced
via MITRE·03:06 PM
DescriptionWeakness
Data Sourced
via NVD·04:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:16 PM
RemedyAffected Software
Advisory Published
via GitHub·11:49 PM
Data Sourced
via GitHub·11:49 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203