CVE-2026-31871

Description

### 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 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. ### Patches The fix escapes single quotes in the sub-key name before interpolating it into the SQL query, preventing breakout from SQL string literals. ### Workarounds There is no known workaround. ### References - GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-gqpp-xgvh-9h7h - Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.5 - Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.31

How to fix CVE-2026-31871

To remediate CVE-2026-31871, upgrade the affected package to a fixed version below.

• —upgrade to 8.6.31 or later
• —upgrade to 9.6.0-alpha.5 or later

Is CVE-2026-31871 being exploited?

Low — EPSS is 0.0%, meaning exploitation activity has not been observed at scale.

Affected packages (2)

• from 0, < 8.6.31, >= 9.0.0, < 9.6.0
• >= 9.0.0-alpha.1, < 9.6.0-alpha.5

CVSS scores

References (5)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2026-31871
• PATCHgithub.com/parse-community/parse-server
• WEBgithub.com/parse-community/parse-server/releases/tag/8.6.31
• WEBgithub.com/parse-community/parse-server/releases/tag/9.6.0-alpha.5