CVE-2026-33508: parse-server · Uncontrolled Recursion
Affects parse-serverSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 9.6.0-alpha.45 or 8.6.56 soon.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.6.0-alpha.45, 8.6.56
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade parse-server to 9.6.0-alpha.45 or 8.6.56; parse-community/parse-server to 8.6.56.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| parse-communityparse-server | Affected
| Fixed in
|
| parse-communityparse-server | Affected
| Fixed in
|
GitHubparse-community/parse-serverpkg:github/parse-community/parse-serverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Organizations should immediately upgrade Parse Server to version 8.6.56 or later, or 9.6.0-alpha.45 or later, where the vulnerability is patched. If upgrading is not immediately feasible, administrators should consider implementing network-level protections such as Web Application Firewalls (WAFs) or rate limiting to detect and block suspiciously complex or deeply nested subscription requests targeting the LiveQuery WebSocket endpoint. Monitoring CPU usage and WebSocket traffic patterns can help identify potential exploitation attempts. Additionally, configuring Parse Server to enforce strict requestComplexity.queryDepth limits and validating subscription queries before processing can reduce risk. Isolating Parse Server instances behind VPNs or restricting access to trusted networks can further limit exposure. Regularly reviewing and applying security updates from the parse-community project is essential to maintain protection against similar vulnerabilities.
Description
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.56 and 9.6.0, Parse Server's LiveQuery component does not enforce the requestComplexity.queryDepth configuration setting when processing WebSocket subscription requests. An attacker can send a subscription with deeply nested logical operators, causing excessive recursion and CPU consumption that degrades or disrupts service availability. This issue has been patched in versions 8.6.56 and 9.6.0
References
- github.com/parse-community/parse-server/security/advisories/GHSA-6qh5-m6g3-xhq6 (opens in a new tab)
- github.com/parse-community/parse-server/pull/10259 (opens in a new tab)
- github.com/parse-community/parse-server/pull/10260 (opens in a new tab)
- github.com/parse-community/parse-server/commit/060d27053fb0fadf613c25aabab7fe0c82b7a899 (opens in a new tab)
- github.com/parse-community/parse-server/commit/2126fe4e12f9b399dc6b4b6a3fa70cb1825f159b (opens in a new tab)