Summary
Parse Server has a LiveQuery protected-field guard bypass via array-like logical operator value
Workarounds
There is no known workaround.
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.
An object is accessed using a type that is incompatible with its actual type, causing the runtime to interpret memory incorrectly. Typical impact: memory safety violations, unexpected behavior, or code execution.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
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.
Frequently Asked Questions
- What is CVE-2026-34595? CVE-2026-34595 is a medium-severity type confusion vulnerability in parse-server (npm), affecting versions >= 9.0.0, < 9.7.0-alpha.16. It is fixed in 9.7.0-alpha.16, 8.6.70. An object is accessed using a type that is incompatible with its actual type, causing the runtime to interpret memory incorrectly.
- Which versions of parse-server are affected by CVE-2026-34595? parse-server (npm) versions >= 9.0.0, < 9.7.0-alpha.16 is affected.
- Is there a fix for CVE-2026-34595? Yes. CVE-2026-34595 is fixed in 9.7.0-alpha.16, 8.6.70. Upgrade to this version or later.
- Is CVE-2026-34595 exploitable, and should I be worried? Whether CVE-2026-34595 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-34595 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-34595?
- Upgrade
parse-serverto 9.7.0-alpha.16 or later - Upgrade
parse-serverto 8.6.70 or later
- Upgrade