{"id":"GHSA-wmwx-jr2p-4j4r","revision":"44eda1ee1d7e4306a84a6c67d3e54984","records":[{"revision":"44eda1ee1d7e4306a84a6c67d3e54984","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"GHSA-wmwx-jr2p-4j4r","aliases":["BIT-parse-2026-53726","CVE-2026-53726"],"title":"parse-server: Relation `$relatedTo` query bypasses `protectedFields` and owning-object ACL","description":"### Impact\n\nA 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.\n\nAs 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.\n\n### Patches\n\nThe relation query path now authorizes `$relatedTo` against the owning object before reading the relation join table, using the caller's authentication context. The relation key is checked against the owning class's `protectedFields` (the query is rejected if the key is protected), and the owning object must be readable by the caller under its class-level permissions, ACL, and pointer permissions; otherwise the relation returns no results. Master and maintenance requests are unaffected. The check is applied consistently whether `$relatedTo` is used at the top level or nested within `$or`, `$and`, or `$nor`.\n\n### Workarounds\n\nThere is no complete workaround without upgrading. As mitigation, applications can avoid exposing sensitive membership through `Relation` fields to untrusted clients, or enforce access on the queried class in a `beforeFind` trigger.","state":0,"publishedAt":"2026-06-19T19:35:19+00:00","modifiedAt":"2026-06-19T19:56:04.4912652+00:00","affected":[{"ecosystem":"npm","name":"parse-server","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"9.0.0"},{"kind":"fixed","version":"9.9.1-alpha.6"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"npm","name":"parse-server","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"8.6.80"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V4","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"MODERATE"}],"references":["https://github.com/parse-community/parse-server/security/advisories/GHSA-wmwx-jr2p-4j4r","https://nvd.nist.gov/vuln/detail/CVE-2026-53726","https://github.com/parse-community/parse-server/pull/10493","https://github.com/parse-community/parse-server/pull/10494","https://github.com/parse-community/parse-server"],"sourceUrl":"https://github.com/advisories/GHSA-wmwx-jr2p-4j4r","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-wmwx-jr2p-4j4r","identifiers":["GHSA-wmwx-jr2p-4j4r","BIT-parse-2026-53726","CVE-2026-53726"]},"retained":false,"historicalAffected":[]}],"coverage":[]}