CVE-2026-53726: parse-server Relation `$relatedTo` Query Bypasses `protectedFields` Vulnerability

MODERATE
Advisory Identifier: GHSA-wmwx-jr2p-4j4r
CWE-639
Published
Advisory Summary

CVE-2026-53726 is a MODERATE relation `$relatedto` query bypasses `protectedfields` vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting parse-server libraries in the npm ecosystem. The issue involves relation `$relatedto` query bypasses `protectedfields` and owning-object acl. Remediation is available by upgrading affected packages to version 9.9.1-alpha.6, 8.6.80.

CVE-2026-53726 at a Glance

CVE Identifier CVE-2026-53726
GHSA Identifier GHSA-wmwx-jr2p-4j4r
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product parse-server
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-53726

To remediate this vulnerability, upgrade all affected parse-server dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

parse-server fixed: 9.9.1-alpha.6
npm install parse-server@9.9.1-alpha.6
parse-server fixed: 8.6.80
npm install parse-server@8.6.80
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls parse-server

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-53726, inspect your project dependencies using npm:

npm ls parse-server

Analyze the terminal output to locate any version of parse-server in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 9.9.1-alpha.6), your application is affected.

Note: The npm ls parse-server command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, where 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. In parse-server, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact 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. ### Patches The 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`. ### Workarounds There 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.

CVE-2026-53726 Affected parse-server Versions

2 component(s)
Fixed Versions:
9.9.1-alpha.68.6.80
Product / Package Ecosystem Affected Versions Fixed Version
parse-server
npm
≥ 9.0.0
< 9.9.1-alpha.6
9.9.1-alpha.6
parse-server
npm
< 8.6.80
8.6.80

References

Frequently Asked Questions

What is CVE-2026-53726?
CVE-2026-53726 is a security vulnerability in parse-server involving Relation `$relatedTo` query bypasses `protectedFields` and owning-object ACL under CWE-639: Authorization Bypass Through User-Controlled Key.
Which parse-server versions are affected?
Affected versions include releases prior to 9.9.1-alpha.6, 8.6.80 across affected packages: parse-server.
What version fixes CVE-2026-53726?
Upgrading to 9.9.1-alpha.6, 8.6.80 (or the latest patched release for your respective branch) resolves the vulnerability.
Is parse-server affected?
Yes, parse-server is affected in releases prior to 9.9.1-alpha.6, 8.6.80. Upgrade your dependency to 9.9.1-alpha.6, 8.6.80 or later.
What CWE is associated with CVE-2026-53726?
CVE-2026-53726 is classified under CWE-639: Authorization Bypass Through User-Controlled Key (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.).
How can I check npm dependencies for CVE-2026-53726?
Run the dependency tree command: 'npm ls parse-server'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-wmwx-jr2p-4j4r",
  "modified" : "2026-06-19T19:35:19Z",
  "published" : "2026-06-19T19:35:19Z",
  "aliases" : [ "CVE-2026-53726" ],
  "summary" : "parse-server: Relation `$relatedTo` query bypasses `protectedFields` and owning-object ACL",
  "details" : "### 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.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "parse-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "9.0.0"
      }, {
        "fixed" : "9.9.1-alpha.6"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "parse-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "8.6.80"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/security/advisories/GHSA-wmwx-jr2p-4j4r"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-53726"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/pull/10493"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/pull/10494"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/parse-community/parse-server"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-639" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-19T19:35:19Z",
    "nvd_published_at" : "2026-06-12T19:16:30Z"
  }
}