CVE-2026-53726
Received Received - Intake
Relation Query Bypass in Parse Server

Publication date: 2026-06-12

Last updated on: 2026-06-12

Assigner: GitHub, Inc.

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.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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-12
Last Modified
2026-06-12
Generated
2026-06-13
AI Q&A
2026-06-12
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 5 associated CPEs
Vendor Product Version / Range
parse_server parse_server to 9.9.1-alpha.6 (exc)
parse parse_server 8.6.80
parse parse_server 9.9.1-alpha.6
parse parse_server From 8.0.0 (inc) to 8.6.80 (exc)
parse parse_server From 9.0.0 (inc) to 9.9.1-alpha.6 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
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.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Compliance Impact

This vulnerability allows unauthorized access to sensitive data by bypassing protected fields and object-level access controls in Parse Server. Specifically, it enables unauthenticated clients to enumerate objects linked through protected relations, such as private group memberships, block lists, or account-to-resource associations, without proper authorization.

Such unauthorized data exposure can lead to violations of data privacy and security requirements mandated by common standards and regulations like GDPR and HIPAA, which require strict controls on access to personal and sensitive information.

Therefore, applications relying on Parse Server versions affected by this vulnerability may face compliance risks due to potential unauthorized disclosure of protected data.

Executive Summary

CVE-2026-53726 is a security vulnerability in Parse Server where the $relatedTo query operator could bypass protectedFields and owning-object Access Control List (ACL) restrictions.

This means that an unauthenticated client, with only public API credentials and knowledge of an object's objectId, could read the membership of a Relation field even if that field was hidden or the owning object was not readable by the client.

As a result, unauthorized users could enumerate objects linked through protected relations, such as private group memberships or block lists, without needing a user session, master key, or Cloud Code access.

The vulnerability was patched in Parse Server versions 8.6.80 and 9.9.1-alpha.6 by enforcing proper authorization checks on $relatedTo queries.

Impact Analysis

This vulnerability can lead to unauthorized disclosure of sensitive data by allowing unauthenticated users to access relation memberships that should be protected.

  • Exposure of private group memberships.
  • Leakage of block lists.
  • Disclosure of account-to-resource associations that rely on protected Relation fields.

Because the attack requires only public API credentials and knowledge of an objectId, it can be exploited remotely with low complexity, potentially compromising confidentiality of protected data.

There is no complete workaround other than upgrading to patched versions; mitigation can include avoiding exposure of sensitive membership data or enforcing access controls in beforeFind triggers.

Detection Guidance

This vulnerability involves unauthorized access through the Parse Server's $relatedTo query operator bypassing protectedFields and ACL restrictions. Detection would involve monitoring for unusual or unauthorized $relatedTo queries that access relation memberships without proper authentication.

Since the vulnerability can be exploited by unauthenticated clients using only public API credentials and knowledge of objectIds, detection could include logging and analyzing API requests for $relatedTo queries that return data from protected relations or objects that should be inaccessible.

Specific commands are not provided in the resources, but general approaches include enabling detailed request logging on the Parse Server and searching logs for $relatedTo queries, especially those that do not have accompanying user session tokens or master keys.

Mitigation Strategies

The primary and recommended mitigation is to upgrade Parse Server to version 8.6.80 or later, or 9.9.1-alpha.6 or later, where the vulnerability has been patched.

If immediate upgrading is not possible, applications can mitigate the risk by avoiding exposure of sensitive membership information through Relation fields or by enforcing access control in beforeFind triggers to restrict unauthorized queries.

No complete workaround exists other than upgrading, so prioritizing the update is critical to prevent unauthorized data exposure.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-53726. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart