BIT-parse-2026-33539: Parse Server: SQL injection via aggregate and distinct field names in PostgreSQL adapter
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.59 and 9.6.0-alpha.53, an attacker with master key access can execute arbitrary SQL statements on the PostgreSQL database by injecting SQL metacharacters into field name parameters of the aggregate $group pipeline stage or the distinct operation. This allows privilege escalation from Parse Server application-level administrator to PostgreSQL database-level access. Only Parse Server deployments using PostgreSQL are affected. MongoDB deployments are not affected. This issue has been patched in versions 8.6.59 and 9.6.0-alpha.53.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Parse Server PostgreSQL adapterto a version that resolves this vulnerability.Fixed in 8.6.59 - Upgrade
Upgrade
Parse Server PostgreSQL adapterto a version that resolves this vulnerability.Fixed in 9.6.0-alpha.53
Event History
Frequently Asked Questions
Which deployments are affected?
Only Parse Server deployments using the PostgreSQL adapter are affected. Deployments using MongoDB are not affected.
What access does an attacker need to exploit this issue?
The attacker needs access to the Parse Server master key. They can then inject SQL metacharacters through field-name parameters in the aggregate $group pipeline stage or the distinct operation.
What is the impact of successful exploitation?
Successful exploitation allows arbitrary SQL statements to be executed on the PostgreSQL database. This can escalate access from a Parse Server application-level administrator to database-level access.
Which versions contain the fix?
The issue is patched in Parse Server versions 8.6.59 and 9.6.0-alpha.53. Versions before those releases are affected when deployed with PostgreSQL.