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.2 and 8.6.28, an attacker can use a dot-notation field name in combination with the sort query parameter to inject SQL into the PostgreSQL database through an improper escaping of sub-field values in dot-notation queries. The vulnerability may also affect queries that use dot-notation field names with the distinct and where query parameters. This vulnerability only affects deployments using a PostgreSQL database. This vulnerability is fixed in 9.6.0-alpha.2 and 8.6.28.
CVE-2026-31840
This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(low)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 34%
- KEV
- Not listed
Published
March 11, 2026
Last Modified
June 17, 2026
Advisory Details (3)
Auto-updated Jul 27, 2026SQL injection via dot-notation field name in PostgreSQL · Advisory · parse-community/parse-server · GitHub
https://github.com/parse-community/parse-server/security/advisories/GHSA-qpr4-jrj4-6f279.6.0-alpha.2
Patch available: parse-community/parse-server 9.6.0-alpha.2 (pre-release)
https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.28.6.28
Patch available: parse-community/parse-server 8.6.28
https://github.com/parse-community/parse-server/releases/tag/8.6.28Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 13:42 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-31840?
When was CVE-2026-31840 disclosed?
Is CVE-2026-31840 actively exploited?
What is the CVSS score of CVE-2026-31840?
How do I remediate CVE-2026-31840?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-31840
Is Your Infrastructure Affected by CVE-2026-31840?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.