Quick answers
- Is CVE-2026-32944 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-32944 being exploited in the wild.
- How severe is CVE-2026-32944?
- High severity, with a CVSS score of 4, published 17 March 2026.
- Which products and versions are affected?
- parse-server (npm) >= 9.0.0, < 9.6.0-alpha.21, SEMVER:introduced=9.0.0,fixed=9.6.0-alpha.21.
- Is there a fix for CVE-2026-32944?
- Yes. parse-server (npm): upgrade to 9.6.0-alpha.21 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-32944 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-32944?
- Check whether you run parse-server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- parse-server (npm): upgrade to 9.6.0-alpha.21 or later
npm install parse-server@9.6.0-alpha.21
Technical details
This vulnerability is a recursive exhaustion flaw (CWE-674) in Parse Server's query condition operator parsing. An unauthenticated attacker can craft a request with deeply nested query operators that consumes stack or memory resources, causing the server process to crash and terminate service for all connected clients. No authentication or user interaction is required; a single network request is sufficient to trigger the denial of service. A fix has been released via a depth limit option (requestComplexity.queryDepth), which is disabled by default to avoid breaking changes. Administrators should upgrade to patched versions (9.6.0-alpha.21 or 8.6.45+) and explicitly enable the depth limit.
Affected products
- Parse Community Parse Server >=9.0.0, <9.6.0-alpha.21; <8.6.45
Identifiers
- CVE-2026-32944
- GHSA-9xp9-j92r-p88v
Timeline
- 2026-03-17: disclosed
- 2026-03-17: patched: Patched versions: 9.6.0-alpha.21 and 8.6.45