Most recent entries from all

BIT-parse-2026-30946 — Parse Server affected by denial-of-service via unbounded query complexity in REST and GraphQL API

Affected: Bitnami: parse

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior 9.5.2 and 8.6.15, 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. This vulnerability is fixed in 9.5.2 and 8.6.15.

EUVD-2026-275515

fkie_cve-2026-30946

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior 9.5.2-alpha.2 and 8.6.15, 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. This vulnerability is fixed in 9.5.2-alpha.2 and 8.6.15.

GHSA-cmj3-wx7h-ffvg — Parse Server affected by denial-of-service via unbounded query complexity in REST and GraphQL API

Affected: npm: parse-server

### 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`, `$dontSelect` - `includeDepth`: Maximum depth of dot-separated `include` paths - `includeCount`: Maximum number of `include` fields per query - `graphQLDepth`: Maximum depth of GraphQL field selections - `graphQLFields`: 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.

### Referen…