parse-community parse-server up to 8.6.79/9.9.1-alpha.5 Private Group relatedTo authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 3.00 |
Summary
A vulnerability categorized as problematic has been discovered in parse-community parse-server up to 8.6.79/9.9.1-alpha.5. Impacted is an unknown function of the component Private Group Handler. Executing a manipulation of the argument relatedTo can lead to authorization. This vulnerability is tracked as CVE-2026-53726. The attack can be launched remotely. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability was found in parse-community parse-server up to 8.6.79/9.9.1-alpha.5. It has been declared as problematic. This vulnerability affects an unknown functionality of the component Private Group Handler. The manipulation of the argument relatedTo with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. As an impact it is known to affect confidentiality. CVE summarizes:
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.80 and 9.9.1-alpha.6, a relation query using the $relatedTo operator could read the membership of a Relation field even when that field was hidden from the requesting client by protectedFields, and even when the object owning the relation was not readable by the client under its ACL or class-level permissions. The request requires only the public API credentials that Parse clients normally carry — no user session, master key, or Cloud Code is needed. As a result, an unauthenticated client who knows or obtains the owning object's objectId could enumerate the objects linked through a protected relation, or combine the operator with an objectId constraint to use it as a membership oracle — confirming whether a specific object is linked to a private parent. This affects applications that rely on protectedFields or object ACLs to keep Relation membership confidential, such as private group memberships, block lists, or account-to-resource associations. This issue has been patched in versions 8.6.80 and 9.9.1-alpha.6.
The advisory is shared for download at github.com. This vulnerability was named CVE-2026-53726 since 06/10/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available.
Upgrading to version 8.6.80 or 9.9.1-alpha.6 eliminates this vulnerability. Applying a patch 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.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
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
- 8.6.56
- 8.6.57
- 8.6.58
- 8.6.59
- 8.6.60
- 8.6.61
- 8.6.62
- 8.6.63
- 8.6.64
- 8.6.65
- 8.6.66
- 8.6.67
- 8.6.68
- 8.6.69
- 8.6.70
- 8.6.71
- 8.6.72
- 8.6.73
- 8.6.74
- 8.6.75
- 8.6.76
- 8.6.77
- 8.6.78
- 8.6.79
- 9.9.1-alpha.0
- 9.9.1-alpha.1
- 9.9.1-alpha.2
- 9.9.1-alpha.3
- 9.9.1-alpha.4
- 9.9.1-alpha.5
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.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
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-639 / 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.80/9.9.1-alpha.6
Patch: github.com
Timeline
06/10/2026 CVE reserved06/12/2026 Advisory disclosed
06/12/2026 VulDB entry created
06/12/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-wmwx-jr2p-4j4r
Status: Confirmed
CVE: CVE-2026-53726 (🔒)
GCVE (CVE): GCVE-0-2026-53726
GCVE (VulDB): GCVE-100-370672
Entry
Created: 06/12/2026 22:26Changes: 06/12/2026 22:26 (69)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.