parse-community parse-server up to 8.6.52/9.6.0-alpha.41 LiveQuery WebSocket Interface authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 1.05 |
Summary
A vulnerability was found in parse-community parse-server up to 8.6.52/9.6.0-alpha.41. It has been rated as problematic. This affects an unknown part of the component LiveQuery WebSocket Interface. This manipulation causes authorization. The identification of this vulnerability is CVE-2026-33421. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised.
Details
A vulnerability has been found in parse-community parse-server up to 8.6.52/9.6.0-alpha.41 and classified as problematic. Affected by this vulnerability is an unknown function of the component LiveQuery WebSocket Interface. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. As an impact it is known to affect confidentiality. 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.53 and 9.6.0-alpha.42, Parse Server's LiveQuery WebSocket interface does not enforce Class-Level Permission (CLP) pointer permissions (readUserFields and pointerFields). Any authenticated user can subscribe to LiveQuery events and receive real-time updates for all objects in classes protected by pointer permissions, regardless of whether the pointer fields on those objects point to the subscribing user. This bypasses the intended read access control, allowing unauthorized access to potentially sensitive data that is correctly restricted via the REST API. This issue has been patched in versions 8.6.53 and 9.6.0-alpha.42.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-33421 since 03/19/2026. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available.
Upgrading to version 8.6.53 or 9.6.0-alpha.42 eliminates this vulnerability. Applying the patch 6c3317aca6eb618ac48f999021ae3ef7766ad1ea 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.
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
- 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
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: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 6.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: AuthorizationCWE: CWE-863 / CWE-285 / CWE-266
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.53/9.6.0-alpha.42
Patch: 6c3317aca6eb618ac48f999021ae3ef7766ad1ea
Timeline
03/19/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-fph2-r4qg-9576
Status: Confirmed
CVE: CVE-2026-33421 (🔒)
GCVE (CVE): GCVE-0-2026-33421
GCVE (VulDB): GCVE-100-352849
Entry
Created: 03/24/2026 20:52Updated: 03/29/2026 06:47
Changes: 03/24/2026 20:52 (69), 03/29/2026 06:47 (12)
Complete: 🔍
Cache ID: 216:119:103
No comments yet. Languages: en.
Please log in to comment.