Parse Server vulnerable to SQL Injection via dot-notation sub-key name in Increment operation on PostgreSQL

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 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 · score source

EPSS

• CVE-2026-31871: 0.43% estimated exploitation activity in the next 30 days; percentile 37.80 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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:…

Published by the source

11 Mar 2026, 00:34 UTC

Last modified by the source

13 Mar 2026, 13:11 UTC

Source last checked

26 Oct 2026, 12:43 UTC

1. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-gqpp-xgvh-9h7h

2. Revision 3 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-gqpp-xgvh-9h7h

4. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-gqpp-xgvh-9h7h

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-31871

Advisory: Parse Server vulnerable to SQL Injection via dot-notation sub-key name in `Increment` operation on PostgreSQL
IDs: CVE-2026-31871, GHSA-gqpp-xgvh-9h7h
Record: https://patchnext.com/advisories/cve-2026-31871 (revision 4, source checked 26 Oct 2026, 12:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: parse-server 9.6.0-alpha.5, 8.6.31. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm parse-server: affected >= 9.0.0-alpha.1, < 9.6.0-alpha.5; < 8.6.31; fixed in 8.6.31, 9.6.0-alpha.5

## Suggested inspection (read-only)
- `npm ls parse-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on parse-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gqpp-xgvh-9h7h (GitHub-reviewed advisory GHSA-gqpp-xgvh-9h7h lists affected ranges: npm parse-server >=9.0.0-alpha.1 =0 <8.6.31)
- Verified: https://osv.dev/vulnerability/GHSA-gqpp-xgvh-9h7h (OSV record GHSA-gqpp-xgvh-9h7h lists affected ranges: npm parse-server >=9.0.0-alpha.1 =0 <8.6.31 (fixed))

Commands are suggestions: review each one before running it.