parse-community parse-server up to 8.6.55/9.6.0-alpha.44 LiveQuery recursion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 1.55 |
Summary
A vulnerability identified as problematic has been detected in parse-community parse-server up to 8.6.55/9.6.0-alpha.44. Affected by this issue is some unknown functionality of the component LiveQuery. This manipulation causes recursion. This vulnerability is tracked as CVE-2026-33508. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability classified as problematic was found in parse-community parse-server up to 8.6.55/9.6.0-alpha.44. Affected by this vulnerability is some unknown functionality of the component LiveQuery. The manipulation with an unknown input leads to a recursion vulnerability. The CWE definition for the vulnerability is CWE-674. The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack. As an impact it is known to affect availability. The summary by CVE is:
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-alpha.45, 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-alpha.45.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-33508 since 03/20/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Upgrading to version 8.6.56 or 9.6.0-alpha.45 eliminates this vulnerability. Applying the patch 060d27053fb0fadf613c25aabab7fe0c82b7a899 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-13917). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 8.6.0
- 8.6.1
- 8.6.2
- 8.6.3
- 8.6.4
- 8.6.5
- 8.6.6
- 8.6.7
- 8.6.8
- 8.6.9
- 8.6.10
- 8.6.11
- 8.6.12
- 8.6.13
- 8.6.14
- 8.6.15
- 8.6.16
- 8.6.17
- 8.6.18
- 8.6.19
- 8.6.20
- 8.6.21
- 8.6.22
- 8.6.23
- 8.6.24
- 8.6.25
- 8.6.26
- 8.6.27
- 8.6.28
- 8.6.29
- 8.6.30
- 8.6.31
- 8.6.32
- 8.6.33
- 8.6.34
- 8.6.35
- 8.6.36
- 8.6.37
- 8.6.38
- 8.6.39
- 8.6.40
- 8.6.41
- 8.6.42
- 8.6.43
- 8.6.44
- 8.6.45
- 8.6.46
- 8.6.47
- 8.6.48
- 8.6.49
- 8.6.50
- 8.6.51
- 8.6.52
- 8.6.53
- 8.6.54
- 8.6.55
- 9.6.0-alpha.0
- 9.6.0-alpha.1
- 9.6.0-alpha.2
- 9.6.0-alpha.3
- 9.6.0-alpha.4
- 9.6.0-alpha.5
- 9.6.0-alpha.6
- 9.6.0-alpha.7
- 9.6.0-alpha.8
- 9.6.0-alpha.9
- 9.6.0-alpha.10
- 9.6.0-alpha.11
- 9.6.0-alpha.12
- 9.6.0-alpha.13
- 9.6.0-alpha.14
- 9.6.0-alpha.15
- 9.6.0-alpha.16
- 9.6.0-alpha.17
- 9.6.0-alpha.18
- 9.6.0-alpha.19
- 9.6.0-alpha.20
- 9.6.0-alpha.21
- 9.6.0-alpha.22
- 9.6.0-alpha.23
- 9.6.0-alpha.24
- 9.6.0-alpha.25
- 9.6.0-alpha.26
- 9.6.0-alpha.27
- 9.6.0-alpha.28
- 9.6.0-alpha.29
- 9.6.0-alpha.30
- 9.6.0-alpha.31
- 9.6.0-alpha.32
- 9.6.0-alpha.33
- 9.6.0-alpha.34
- 9.6.0-alpha.35
- 9.6.0-alpha.36
- 9.6.0-alpha.37
- 9.6.0-alpha.38
- 9.6.0-alpha.39
- 9.6.0-alpha.40
- 9.6.0-alpha.41
- 9.6.0-alpha.42
- 9.6.0-alpha.43
- 9.6.0-alpha.44
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: RecursionCWE: CWE-674 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: parse-server 8.6.56/9.6.0-alpha.45
Patch: 060d27053fb0fadf613c25aabab7fe0c82b7a899
Timeline
03/20/2026 CVE reserved03/24/2026 Advisory disclosed
03/24/2026 VulDB entry created
03/29/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-6qh5-m6g3-xhq6
Status: Confirmed
CVE: CVE-2026-33508 (🔒)
GCVE (CVE): GCVE-0-2026-33508
GCVE (VulDB): GCVE-100-352837
EUVD: 🔒
Entry
Created: 03/24/2026 20:47Updated: 03/29/2026 09:02
Changes: 03/24/2026 20:47 (69), 03/24/2026 21:59 (1), 03/29/2026 09:02 (12)
Complete: 🔍
Cache ID: 216:A79:103
No comments yet. Languages: en.
Please log in to comment.