CVE-2026-32098

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

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.

Kodem intelligence

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.

1. What is CVE-2026-32098? CVE-2026-32098 is a medium-severity security vulnerability in parse-server (npm), affecting versions >= 9.0.0, < 9.6.0-alpha.9. It is fixed in 9.6.0-alpha.9, 8.6.35.
2. Which versions of parse-server are affected by CVE-2026-32098? parse-server (npm) versions >= 9.0.0, < 9.6.0-alpha.9 is affected.
3. Is there a fix for CVE-2026-32098? Yes. CVE-2026-32098 is fixed in 9.6.0-alpha.9, 8.6.35. Upgrade to this version or later.
4. Is CVE-2026-32098 exploitable, and should I be worried? Whether CVE-2026-32098 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
5. What actually determines whether CVE-2026-32098 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.
6. How do I fix CVE-2026-32098?
   • Upgrade parse-server to 9.6.0-alpha.9 or later
   • Upgrade parse-server to 8.6.35 or later

Other vulnerabilities in parse-server