CVE-2026-34595: Parse server Parse Server Has A LiveQuery Vulnerability

MODERATE
Advisory Identifier: GHSA-mmg8-87c5-jrc2
CWE-843
Published
Advisory Summary

CVE-2026-34595 is a MODERATE parse server has a livequery vulnerability (CWE-843: Access of Resource Using Incompatible Type ('Type Confusion')) affecting Parse server libraries in the npm ecosystem. The issue involves parse server has a livequery protected-field guard bypass via array-like logical operator value. Remediation is available by upgrading affected packages to version 9.7.0-alpha.16, 8.6.70.

CVE-2026-34595 at a Glance

CVE Identifier CVE-2026-34595
GHSA Identifier GHSA-mmg8-87c5-jrc2
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-843: Access of Resource Using Incompatible Type ('Type Confusion')
Affected Product Parse server
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-34595

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.7.0-alpha.16
npm install parse-server@9.7.0-alpha.16
parse-server fixed: 8.6.70
npm install parse-server@8.6.70
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-34595, 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.7.0-alpha.16), 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-843: Access of Resource Using Incompatible Type ('Type Confusion'), where the product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type. 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 authenticated user with `find` class-level permission can bypass the `protectedFields` class-level permission setting on LiveQuery subscriptions. By sending a subscription with a `$or`, `$and`, or `$nor` operator value as a plain object with numeric keys and a `length` property (an "array-like" object) instead of an array, the protected-field guard is bypassed. The subscription event firing acts as a binary oracle, allowing the attacker to infer whether a protected field matches a given test value. ### Patches The fix validates that `$or`, `$and`, and `$nor` operator values are arrays in the LiveQuery subscription handler, the query depth checker, and the protected-field guard. As defense in depth, the LiveQuery query evaluator also rejects non-array values for these operators. ### Workarounds There is no known workaround.

CVE-2026-34595 Affected Parse server Versions

2 component(s)
Fixed Versions:
9.7.0-alpha.168.6.70
Product / Package Ecosystem Affected Versions Fixed Version
parse-server
npm
≥ 9.0.0
< 9.7.0-alpha.16
9.7.0-alpha.16
parse-server
npm
< 8.6.70
8.6.70

References

Frequently Asked Questions

What is CVE-2026-34595?
CVE-2026-34595 is a security vulnerability in Parse server involving Parse Server has a LiveQuery protected-field guard bypass via array-like logical operator value under CWE-843: Access of Resource Using Incompatible Type ('Type Confusion').
Which Parse server versions are affected?
Affected versions include releases prior to 9.7.0-alpha.16, 8.6.70 across affected packages: parse-server.
What version fixes CVE-2026-34595?
Upgrading to 9.7.0-alpha.16, 8.6.70 (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.7.0-alpha.16, 8.6.70. Upgrade your dependency to 9.7.0-alpha.16, 8.6.70 or later.
What CWE is associated with CVE-2026-34595?
CVE-2026-34595 is classified under CWE-843: Access of Resource Using Incompatible Type ('Type Confusion') (The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.).
How can I check npm dependencies for CVE-2026-34595?
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-mmg8-87c5-jrc2",
  "modified" : "2026-04-01T00:07:39Z",
  "published" : "2026-04-01T00:07:39Z",
  "aliases" : [ "CVE-2026-34595" ],
  "summary" : "Parse Server has a LiveQuery protected-field guard bypass via array-like logical operator value",
  "details" : "### Impact\n\nAn authenticated user with `find` class-level permission can bypass the `protectedFields` class-level permission setting on LiveQuery subscriptions. By sending a subscription with a `$or`, `$and`, or `$nor` operator value as a plain object with numeric keys and a `length` property (an \"array-like\" object) instead of an array, the protected-field guard is bypassed. The subscription event firing acts as a binary oracle, allowing the attacker to infer whether a protected field matches a given test value.\n\n### Patches\n\nThe fix validates that `$or`, `$and`, and `$nor` operator values are arrays in the LiveQuery subscription handler, the query depth checker, and the protected-field guard. As defense in depth, the LiveQuery query evaluator also rejects non-array values for these operators.\n\n### Workarounds\n\nThere is no known workaround.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/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.7.0-alpha.16"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "parse-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "8.6.70"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/security/advisories/GHSA-mmg8-87c5-jrc2"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-34595"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/pull/10350"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/pull/10351"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/commit/f63fd1a3fe0a7c1c5fe809f01b0e04759e8c9b98"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/commit/ffad0ec6b971ee0dd9545e1bf1fb34ddebf275c2"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/parse-community/parse-server"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-843" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-01T00:07:39Z",
    "nvd_published_at" : "2026-03-31T16:16:34Z"
  }
}