CVE-2026-31871 json
Parse Server has a SQL Injection via dot-notation sub-key name in `Increment` operation on PostgreSQL
published 7mo ago modified 2mo ago also BIT-parse-2026-31871 , EUVD-2026-11277 , GHSA-gqpp-xgvh-9h7h
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.6.0-alpha.5 and 8.6.31, 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 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. Only Postgres deployments are affected. This vulnerability is fixed in 9.6.0-alpha.5 and 8.6.31.
Patch / fix
- npm parse-server 8.6.31, 9.6.0-alpha.5
- bitnami parse 8.6.31, 9.6.0
- parseplatform parse-server 8.6.31, 9.6.0-alpha.5
- parseplatform parse_server 8.6.31, 9.6.0-alpha.5
Is CVE-2026-31871 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 7mo ago
Exploit prediction
0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.3 | 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 |
| CNA | 4.0 | 9.3 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | parse-server | >=9.0.0-alpha.1, <9.6.0-alpha.5 <8.6.31 |
9.6.0-alpha.5 8.6.31 |
| bitnami | parse | <8.6.31 >=9.0.0, <9.6.0 |
8.6.31 9.6.0 |
Affected products
- parse-community parse-server
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
github.com
/parse-community/parse-server/security/advisories/GHSA-gqpp-xgvh-9h7h
web, patch, vendor-advisory, advisory
-
github.com
/parse-community/parse-server/releases/tag/8.6.31
web, product, release-notes, article
-
github.com
/parse-community/parse-server/releases/tag/9.6.0-alpha.5
web, product, release-notes, article
-
nvd.nist.gov
/vuln/detail/CVE-2026-31871
advisory, web
-
github.com
/parse-community/parse-server
package
Sources
- CVE List CVE-2026-31871
- GitHub Advisory GHSA-gqpp-xgvh-9h7h
- NVD CVE-2026-31871
- OSV BIT-parse-2026-31871
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.