Summary
Workarounds
Use a beforeFind trigger on affected classes to manually inspect the query for protected field references in logical operator sub-queries and reject the request.
References
- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-72hp-qff8-4pvv
- Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.2-alpha.6
- Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.19
Impact
The validation for protected fields only checks top-level query keys. By wrapping a query constraint on a protected field inside a logical operator, the check is bypassed entirely. This allows any authenticated user to query on protected fields to extract field values.
All Parse Server deployments have default protected fields and are vulnerable.
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.
Remediation advice
The fix adds recursive validation of sub-queries with logical operators, consistent with the existing recursive validation patterns.
Frequently Asked Questions
- What is CVE-2026-30962? CVE-2026-30962 is a high-severity security vulnerability in parse-server (npm), affecting versions >= 9.0.0, < 9.5.2-alpha.6. It is fixed in 9.5.2-alpha.6, 8.6.19.
- Which versions of parse-server are affected by CVE-2026-30962? parse-server (npm) versions >= 9.0.0, < 9.5.2-alpha.6 is affected.
- Is there a fix for CVE-2026-30962? Yes. CVE-2026-30962 is fixed in 9.5.2-alpha.6, 8.6.19. Upgrade to this version or later.
- Is CVE-2026-30962 exploitable, and should I be worried? Whether CVE-2026-30962 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-30962 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-30962?
- Upgrade
parse-serverto 9.5.2-alpha.6 or later - Upgrade
parse-serverto 8.6.19 or later
- Upgrade