CVE-2026-53726: CWE-639: Authorization Bypass Through User-Controlled Key in parse-community parse-server
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.
AI Analysis
Technical Summary
CVE-2026-53726 is an authorization bypass vulnerability in parse-community's parse-server affecting versions prior to 8.6.80 and 9.9.1-alpha.6. The vulnerability arises from improper enforcement of access controls on Relation fields when using the $relatedTo operator in queries. Specifically, clients with only public API credentials can read Relation memberships even if the Relation field is hidden by protectedFields or the owning object is not readable under ACL or class-level permissions. This allows unauthenticated clients to enumerate or confirm membership in protected relations, potentially exposing sensitive association data. The vulnerability impacts applications that depend on protectedFields or ACLs to secure Relation memberships. The issue has been fixed in versions 8.6.80 and 9.9.1-alpha.6.
Potential Impact
An unauthenticated attacker with knowledge or guess of an object's objectId can bypass intended access controls to enumerate or confirm membership in Relation fields that should be confidential. This compromises privacy of protected relations such as private group memberships, block lists, or account-resource associations. No user session, master key, or Cloud Code privileges are required, only the public API credentials normally available to Parse clients. This leads to unauthorized disclosure of sensitive relationship data.
Mitigation Recommendations
This vulnerability has been patched in parse-server versions 8.6.80 and 9.9.1-alpha.6. Users should upgrade to these or later versions to remediate the issue. Patch status is not explicitly stated as official-fix or temporary-fix in the advisory, but the vendor has released fixed versions. Until upgrading, applications relying on protectedFields or ACLs for Relation confidentiality remain vulnerable. No other vendor-provided mitigations or workarounds are indicated.
CVE-2026-53726: CWE-639: Authorization Bypass Through User-Controlled Key in parse-community parse-server
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 v4.0
Score 6.9medium
Affected software
pkg:github/parse-community/parse-serverRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-53726 is an authorization bypass vulnerability in parse-community's parse-server affecting versions prior to 8.6.80 and 9.9.1-alpha.6. The vulnerability arises from improper enforcement of access controls on Relation fields when using the $relatedTo operator in queries. Specifically, clients with only public API credentials can read Relation memberships even if the Relation field is hidden by protectedFields or the owning object is not readable under ACL or class-level permissions. This allows unauthenticated clients to enumerate or confirm membership in protected relations, potentially exposing sensitive association data. The vulnerability impacts applications that depend on protectedFields or ACLs to secure Relation memberships. The issue has been fixed in versions 8.6.80 and 9.9.1-alpha.6.
Potential Impact
An unauthenticated attacker with knowledge or guess of an object's objectId can bypass intended access controls to enumerate or confirm membership in Relation fields that should be confidential. This compromises privacy of protected relations such as private group memberships, block lists, or account-resource associations. No user session, master key, or Cloud Code privileges are required, only the public API credentials normally available to Parse clients. This leads to unauthorized disclosure of sensitive relationship data.
Mitigation Recommendations
This vulnerability has been patched in parse-server versions 8.6.80 and 9.9.1-alpha.6. Users should upgrade to these or later versions to remediate the issue. Patch status is not explicitly stated as official-fix or temporary-fix in the advisory, but the vendor has released fixed versions. Until upgrading, applications relying on protectedFields or ACLs for Relation confidentiality remain vulnerable. No other vendor-provided mitigations or workarounds are indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-10T16:43:31.242Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a2c5615e617e2d834b0f485
Added to database: 6/12/2026, 6:55:17 PM
Last enriched: 6/12/2026, 7:09:53 PM
Last updated: 6/12/2026, 8:20:33 PM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.