GHSA-97pr-9hgg-3p8r: parse-server LiveQuery Discloses Object Data To Vulnerability

LOW
Share
CWE-200
Published
Advisory Summary

GHSA-97pr-9hgg-3p8r is a LOW livequery discloses object data to vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting parse-server libraries in the npm ecosystem. The issue involves livequery discloses object data to a subscriber across an acl read-access change. Remediation is available by upgrading affected packages to version 9.9.1-alpha.13, 8.6.83.

GHSA-97pr-9hgg-3p8r at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-97pr-9hgg-3p8r
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product parse-server
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-97pr-9hgg-3p8r

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.13 
npm install parse-server@9.9.1-alpha.13
parse-server fixed: 8.6.83 
npm install parse-server@8.6.83
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 GHSA-97pr-9hgg-3p8r, 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.13), 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-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. 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 Parse Server LiveQuery subscriber can receive object field values they are not authorized to read when a single `save` changes both an object field and the subscriber's ACL read access to that object. When such a save removes the subscriber's read access, the resulting `leave` event still carries the post-update object body, disclosing the new field values the subscriber is no longer permitted to read. The symmetric case applies to the `enter` event: when a save grants read access, the event includes the pre-grant object state the subscriber was not previously permitted to read. The disclosure is bounded to the single object affected by that save and is delivered only to the subscriber whose access changed. Applications that combine content changes with access-control changes in the same save on LiveQuery-enabled classes are affected. ### Patches Parse Server now verifies the subscriber's authorization for the specific object state included in `leave` and `enter` events. For a `leave` caused by the subscriber losing read access, the event delivers the last object state the subscriber was authorized to see instead of the post-update body. For an `enter` caused by the subscriber gaining read access, the previously unauthorized original object state is omitted. Events caused by a normal query-match change, where the subscriber keeps read access, are unaffected, as are master-key subscribers. ### Workarounds Do not change an object's field values and a subscriber's ACL read access in the same `save` on LiveQuery-enabled classes; perform the access-control change in a separate save before or after the content change. Alternatively, limit which classes are enabled for LiveQuery.

GHSA-97pr-9hgg-3p8r Affected parse-server Versions

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

References

GitHub Advisory / Wiki ADVISORY
https://github.com/parse-community/parse-server/security/advisories/GHSA-97pr-9hgg-3p8r
parse-server Source Repository REPOSITORY
https://github.com/parse-community/parse-server/pull/10515
parse-server Source Repository REPOSITORY
https://github.com/parse-community/parse-server/pull/10516
parse-server Source Repository REPOSITORY
https://github.com/parse-community/parse-server

Frequently Asked Questions

What is GHSA-97pr-9hgg-3p8r?
GHSA-97pr-9hgg-3p8r is a security vulnerability in parse-server involving LiveQuery discloses object data to a subscriber across an ACL read-access change under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which parse-server versions are affected?
Affected versions include releases prior to 9.9.1-alpha.13, 8.6.83 across affected packages: parse-server.
What version fixes GHSA-97pr-9hgg-3p8r?
Upgrading to 9.9.1-alpha.13, 8.6.83 (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.13, 8.6.83. Upgrade your dependency to 9.9.1-alpha.13, 8.6.83 or later.
What CWE is associated with GHSA-97pr-9hgg-3p8r?
GHSA-97pr-9hgg-3p8r is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check npm dependencies for GHSA-97pr-9hgg-3p8r?
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
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-97pr-9hgg-3p8r",
  "modified" : "2026-06-19T21:42:48Z",
  "published" : "2026-06-19T21:42:48Z",
  "aliases" : [ ],
  "summary" : "parse-server: LiveQuery discloses object data to a subscriber across an ACL read-access change",
  "details" : "### Impact\n\nA Parse Server LiveQuery subscriber can receive object field values they are not authorized to read when a single `save` changes both an object field and the subscriber's ACL read access to that object. When such a save removes the subscriber's read access, the resulting `leave` event still carries the post-update object body, disclosing the new field values the subscriber is no longer permitted to read. The symmetric case applies to the `enter` event: when a save grants read access, the event includes the pre-grant object state the subscriber was not previously permitted to read. The disclosure is bounded to the single object affected by that save and is delivered only to the subscriber whose access changed. Applications that combine content changes with access-control changes in the same save on LiveQuery-enabled classes are affected.\n\n### Patches\n\nParse Server now verifies the subscriber's authorization for the specific object state included in `leave` and `enter` events. For a `leave` caused by the subscriber losing read access, the event delivers the last object state the subscriber was authorized to see instead of the post-update body. For an `enter` caused by the subscriber gaining read access, the previously unauthorized original object state is omitted. Events caused by a normal query-match change, where the subscriber keeps read access, are unaffected, as are master-key subscribers.\n\n### Workarounds\n\nDo not change an object's field values and a subscriber's ACL read access in the same `save` on LiveQuery-enabled classes; perform the access-control change in a separate save before or after the content change. Alternatively, limit which classes are enabled for LiveQuery.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/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.13"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "parse-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "8.6.83"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 8.6.82"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/security/advisories/GHSA-97pr-9hgg-3p8r"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/pull/10515"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/pull/10516"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/parse-community/parse-server"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-19T21:42:48Z",
    "nvd_published_at" : null
  }
}