Parse Server: Relation `$relatedTo` query bypasses `protectedFields` and owning-object ACL

Summary

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.

Timeline

1. Jun 12, 2026, 6:37 PM UTCCVE published
2. Jun 12, 2026, 6:56 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: yes · Technical impact: partial

3. Jun 12, 2026, 6:57 PM UTCRecord last updated

Affected versions

• parse-community parse-server

  fixed in 8.6.80; From 9.0.0 · fixed in 9.9.1-alpha.6

• parse-servernpm

  From 9.0.0 · fixed in 9.9.1-alpha.6

• parse-servernpm

  fixed in 8.6.80

References 3