CVE-2026-31871: Parse server SQL Injection Vulnerability
CRITICALCVE-2026-31871 is a CRITICAL sql injection vulnerability (CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')) affecting Parse server libraries in the npm ecosystem. The issue involves parse server vulnerable to sql injection via dot-notation sub-key name in `increment` operation on postgresql. Remediation is available by upgrading affected packages to version 9.6.0-alpha.5, 8.6.31.
CVE-2026-31871 at a Glance
How to Fix CVE-2026-31871
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.
npm install parse-server@9.6.0-alpha.5
npm install parse-server@8.6.31
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-31871, 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.6.0-alpha.5), 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-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'), where the product constructs all or part of an sql command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended sql command when it is sent to a downstream component. without sufficient removal or quoting of sql syntax in user-controllable inputs, the generated sql query can cause those inputs to be interpreted as sql instead of ordinary user data. 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
CVE-2026-31871 Affected Parse server Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
parse-server
|
npm |
≥ 9.0.0-alpha.1
< 9.6.0-alpha.5
|
9.6.0-alpha.5
|
|
parse-server
|
npm |
< 8.6.31
|
8.6.31
|
References
Frequently Asked Questions
What is CVE-2026-31871?
Which Parse server versions are affected?
What version fixes CVE-2026-31871?
Is parse-server affected?
What CWE is associated with CVE-2026-31871?
How can I check npm dependencies for CVE-2026-31871?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-gqpp-xgvh-9h7h",
"modified" : "2026-03-11T20:57:43Z",
"published" : "2026-03-11T00:34:40Z",
"aliases" : [ "CVE-2026-31871" ],
"summary" : "Parse Server vulnerable to SQL Injection via dot-notation sub-key name in `Increment` operation on PostgreSQL",
"details" : "### Impact\n\nA 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 sub-key name is interpolated directly into SQL string literals without escaping. An attacker who can send write requests to the Parse Server REST API can inject arbitrary SQL via a crafted sub-key name containing single quotes, potentially executing commands or reading data from the database, bypassing CLPs and ACLs.\n\nOnly Postgres deployments are affected.\n\n### Patches\n\nThe fix escapes single quotes in the sub-key name before interpolating it into the SQL query, preventing breakout from SQL string literals.\n\n### Workarounds\n\nThere is no known workaround.\n\n### References\n\n- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-gqpp-xgvh-9h7h\n- Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.5\n- Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.31",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "parse-server"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "9.0.0-alpha.1"
}, {
"fixed" : "9.6.0-alpha.5"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "parse-server"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "8.6.31"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/parse-community/parse-server/security/advisories/GHSA-gqpp-xgvh-9h7h"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-31871"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/parse-community/parse-server"
}, {
"type" : "WEB",
"url" : "https://github.com/parse-community/parse-server/releases/tag/8.6.31"
}, {
"type" : "WEB",
"url" : "https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.5"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-89" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2026-03-11T00:34:40Z",
"nvd_published_at" : "2026-03-11T18:16:26Z"
}
}