CVE-2026-32098: Parse server Parse Server Has A Protected Vulnerability

MODERATE
Advisory Identifier: GHSA-j7mm-f4rv-6q6q
Share
CWE-200
Published
Advisory Summary

CVE-2026-32098 is a MODERATE parse server has a protected vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Parse server libraries in the npm ecosystem. The issue involves parse server has a protected fields bypass via livequery subscription where clause. Remediation is available by upgrading affected packages to version 9.6.0-alpha.9, 8.6.35.

CVE-2026-32098 at a Glance

CVE Identifier CVE-2026-32098
GHSA Identifier GHSA-j7mm-f4rv-6q6q
Severity MODERATE
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 CVE-2026-32098

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.6.0-alpha.9 
npm install parse-server@9.6.0-alpha.9
parse-server fixed: 8.6.35 
npm install parse-server@8.6.35
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-32098, 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.6.0-alpha.9), 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 An attacker can exploit LiveQuery subscriptions to infer the values of protected fields without directly receiving them. By subscribing with a WHERE clause that references a protected field (including via dot-notation or `$regex`), the attacker can observe whether LiveQuery events are delivered for matching objects. This creates a boolean oracle that leaks protected field values. The attack affects any class that has both `protectedFields` configured in Class-Level Permissions and LiveQuery enabled. ### Patches The fix adds validation of the LiveQuery subscription WHERE clause against the class's protected fields, mirroring the existing REST API validation. If a subscription's WHERE clause references a protected field directly, via dot-notation, or inside `$or` / `$and` / `$nor` operators, the subscription is rejected with a permission error. This is applied during subscription creation, so existing event delivery paths are not affected. ### Workarounds Disable LiveQuery for classes that use `protectedFields` in their Class-Level Permissions, or remove `protectedFields` from classes that require LiveQuery. ### References - GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-j7mm-f4rv-6q6q - Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.9 - Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.35

CVE-2026-32098 Affected Parse server Versions

2 component(s)
Fixed Versions:
9.6.0-alpha.98.6.35
Product / Package Ecosystem Affected Versions Fixed Version
parse-server
npm/parse-server
npm
≥ 9.0.0
< 9.6.0-alpha.9
9.6.0-alpha.9
parse-server
npm/parse-server
npm
< 8.6.35
8.6.35

References

GitHub Advisory / Wiki ADVISORY
https://github.com/parse-community/parse-server/security/advisories/GHSA-j7mm-f4rv-6q6q
NVD — CVE-2026-32098 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-32098
Parse server Source Repository REPOSITORY
https://github.com/parse-community/parse-server
Parse server Release RELEASE
https://github.com/parse-community/parse-server/releases/tag/8.6.35
Parse server Release RELEASE
https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.9

Frequently Asked Questions

What is CVE-2026-32098?
CVE-2026-32098 is a security vulnerability in Parse server involving Parse Server has a protected fields bypass via LiveQuery subscription WHERE clause under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Parse server versions are affected?
Affected versions include releases prior to 9.6.0-alpha.9, 8.6.35 across affected packages: parse-server.
What version fixes CVE-2026-32098?
Upgrading to 9.6.0-alpha.9, 8.6.35 (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.6.0-alpha.9, 8.6.35. Upgrade your dependency to 9.6.0-alpha.9, 8.6.35 or later.
What CWE is associated with CVE-2026-32098?
CVE-2026-32098 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 CVE-2026-32098?
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-j7mm-f4rv-6q6q",
  "modified" : "2026-03-12T14:20:02Z",
  "published" : "2026-03-12T14:20:02Z",
  "aliases" : [ "CVE-2026-32098" ],
  "summary" : "Parse Server has a protected fields bypass via LiveQuery subscription WHERE clause",
  "details" : "### Impact\n\nAn attacker can exploit LiveQuery subscriptions to infer the values of protected fields without directly receiving them. By subscribing with a WHERE clause that references a protected field (including via dot-notation or `$regex`), the attacker can observe whether LiveQuery events are delivered for matching objects. This creates a boolean oracle that leaks protected field values. The attack affects any class that has both `protectedFields` configured in Class-Level Permissions and LiveQuery enabled.\n\n### Patches\n\nThe fix adds validation of the LiveQuery subscription WHERE clause against the class's protected fields, mirroring the existing REST API validation. If a subscription's WHERE clause references a protected field directly, via dot-notation, or inside `$or` / `$and` / `$nor` operators, the subscription is rejected with a permission error. This is applied during subscription creation, so existing event delivery paths are not affected.\n\n### Workarounds\n\nDisable LiveQuery for classes that use `protectedFields` in their Class-Level Permissions, or remove `protectedFields` from classes that require LiveQuery.\n\n### References\n\n- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-j7mm-f4rv-6q6q\n- Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.9\n- Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.35",
  "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.6.0-alpha.9"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "parse-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "8.6.35"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/security/advisories/GHSA-j7mm-f4rv-6q6q"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-32098"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/parse-community/parse-server"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/releases/tag/8.6.35"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.9"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-12T14:20:02Z",
    "nvd_published_at" : "2026-03-11T20:16:18Z"
  }
}