BIT-parse-2026-33539: Parse Server: SQL injection via aggregate and distinct field names in PostgreSQL adapter

Published Mar 24, 2026
·
Updated

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

1 affected component
Parse Platform Parse Server<8.6.59, <9.6.0-alpha.53

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Parse Server PostgreSQL adapter to a version that resolves this vulnerability.

    Fixed in 8.6.59
  2. Upgrade

    Upgrade Parse Server PostgreSQL adapter to a version that resolves this vulnerability.

    Fixed in 9.6.0-alpha.53

Event History

Mar 24, 2026
CVE Published
via OSV·06:26 PM
Data Sourced
via OSV·06:26 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

Only Parse Server deployments using the PostgreSQL adapter are affected. Deployments using MongoDB are not affected.

2

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.

3

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.

4

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203