Summary
Workarounds
There is no known workaround.
References
- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-q3vj-96h2-gwvg
- Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.3
- Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.29
Impact
A SQL injection vulnerability exists in the PostgreSQL storage adapter when processing Increment operations on nested object fields using dot notation (e.g., stats.counter). The amount value is interpolated directly into the SQL query without parameterization or type validation. An attacker who can send write requests to the Parse Server REST API can inject arbitrary SQL subqueries to read any data from the database, bypassing CLPs and ACLs.
MongoDB deployments are not affected.
Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.
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 type validation to reject non-number values and parameterizes the value in the SQL query instead of interpolating it.
Frequently Asked Questions
- What is CVE-2026-31856? CVE-2026-31856 is a critical-severity SQL injection vulnerability in parse-server (npm), affecting versions >= 9.0.0-alpha.1, < 9.6.0-alpha.3. It is fixed in 9.6.0-alpha.3, 8.6.29. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
- Which versions of parse-server are affected by CVE-2026-31856? parse-server (npm) versions >= 9.0.0-alpha.1, < 9.6.0-alpha.3 is affected.
- Is there a fix for CVE-2026-31856? Yes. CVE-2026-31856 is fixed in 9.6.0-alpha.3, 8.6.29. Upgrade to this version or later.
- Is CVE-2026-31856 exploitable, and should I be worried? Whether CVE-2026-31856 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-31856 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-31856?
- Upgrade
parse-serverto 9.6.0-alpha.3 or later - Upgrade
parse-serverto 8.6.29 or later
- Upgrade