CVE-2026-31840

Workarounds

There is no known workaround.

References

• GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-qpr4-jrj4-6f27
• Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.2
• Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/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.

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.

Kodem intelligence

The fix escapes characters in dot-notation sub-field values that could allow a SQL breakout.

1. What is CVE-2026-31840? CVE-2026-31840 is a critical-severity SQL injection vulnerability in parse-server (npm), affecting versions >= 9.0.0, < 9.6.0-alpha.2. It is fixed in 9.6.0-alpha.2, 8.6.28. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
2. Which versions of parse-server are affected by CVE-2026-31840? parse-server (npm) versions >= 9.0.0, < 9.6.0-alpha.2 is affected.
3. Is there a fix for CVE-2026-31840? Yes. CVE-2026-31840 is fixed in 9.6.0-alpha.2, 8.6.28. Upgrade to this version or later.
4. Is CVE-2026-31840 exploitable, and should I be worried? Whether CVE-2026-31840 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
5. What actually determines whether CVE-2026-31840 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.
6. How do I fix CVE-2026-31840?
   • Upgrade parse-server to 9.6.0-alpha.2 or later
   • Upgrade parse-server to 8.6.28 or later

Other vulnerabilities in parse-server