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

Published Mar 24, 2026
·
Updated

Impact

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.

Patches

Field names in the aggregate $group.id object values and distinct dot-notation parameters are now validated to only contain alphanumeric characters and underscores, preventing SQL injection via the :raw interpolation used in the PostgreSQL storage adapter.

Workarounds

No workaround. Upgrade to a patched version.

Other sources

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.

MITRE

Affected Software

57 affected componentsFixes available
Parse Platform Parse Server (PostgreSQL adapter)<8.6.59, <9.6.0-alpha.53
npm/parse-server<8.6.59
8.6.59
npm/parse-server>=9.0.0<9.6.0-alpha.53
9.6.0-alpha.53
parseplatform Parse-server Node.js<8.6.59
parseplatform Parse-server Node.js>=9.0.0<9.6.0
parseplatform Parse-server Node.js=9.6.0-alpha1
parseplatform Parse-server Node.js=9.6.0-alpha10
parseplatform Parse-server Node.js=9.6.0-alpha11
parseplatform Parse-server Node.js=9.6.0-alpha12
parseplatform Parse-server Node.js=9.6.0-alpha13
parseplatform Parse-server Node.js=9.6.0-alpha14
parseplatform Parse-server Node.js=9.6.0-alpha15
parseplatform Parse-server Node.js=9.6.0-alpha16
parseplatform Parse-server Node.js=9.6.0-alpha17
parseplatform Parse-server Node.js=9.6.0-alpha18
parseplatform Parse-server Node.js=9.6.0-alpha19
parseplatform Parse-server Node.js=9.6.0-alpha2
parseplatform Parse-server Node.js=9.6.0-alpha20
parseplatform Parse-server Node.js=9.6.0-alpha21
parseplatform Parse-server Node.js=9.6.0-alpha22
parseplatform Parse-server Node.js=9.6.0-alpha23
parseplatform Parse-server Node.js=9.6.0-alpha24
parseplatform Parse-server Node.js=9.6.0-alpha25
parseplatform Parse-server Node.js=9.6.0-alpha26
parseplatform Parse-server Node.js=9.6.0-alpha27
parseplatform Parse-server Node.js=9.6.0-alpha28
parseplatform Parse-server Node.js=9.6.0-alpha29
parseplatform Parse-server Node.js=9.6.0-alpha3
parseplatform Parse-server Node.js=9.6.0-alpha30
parseplatform Parse-server Node.js=9.6.0-alpha31
parseplatform Parse-server Node.js=9.6.0-alpha32
parseplatform Parse-server Node.js=9.6.0-alpha33
parseplatform Parse-server Node.js=9.6.0-alpha34
parseplatform Parse-server Node.js=9.6.0-alpha35
parseplatform Parse-server Node.js=9.6.0-alpha36
parseplatform Parse-server Node.js=9.6.0-alpha37
parseplatform Parse-server Node.js=9.6.0-alpha38
parseplatform Parse-server Node.js=9.6.0-alpha39
parseplatform Parse-server Node.js=9.6.0-alpha4
parseplatform Parse-server Node.js=9.6.0-alpha40
parseplatform Parse-server Node.js=9.6.0-alpha41
parseplatform Parse-server Node.js=9.6.0-alpha42
parseplatform Parse-server Node.js=9.6.0-alpha43
parseplatform Parse-server Node.js=9.6.0-alpha44
parseplatform Parse-server Node.js=9.6.0-alpha45
parseplatform Parse-server Node.js=9.6.0-alpha46
parseplatform Parse-server Node.js=9.6.0-alpha47
parseplatform Parse-server Node.js=9.6.0-alpha48
parseplatform Parse-server Node.js=9.6.0-alpha49
parseplatform Parse-server Node.js=9.6.0-alpha5
parseplatform Parse-server Node.js=9.6.0-alpha50
parseplatform Parse-server Node.js=9.6.0-alpha51
parseplatform Parse-server Node.js=9.6.0-alpha52
parseplatform Parse-server Node.js=9.6.0-alpha6
parseplatform Parse-server Node.js=9.6.0-alpha7
parseplatform Parse-server Node.js=9.6.0-alpha8
parseplatform Parse-server Node.js=9.6.0-alpha9

Event History

Mar 24, 2026
CVE Published
via MITRE·06:26 PM
Data Sourced
via MITRE·06:26 PM
DescriptionWeakness
Advisory Published
via GitHub·07:12 PM
Data Sourced
via GitHub·07:12 PM
DescriptionWeaknessAffected Software
Data Sourced
via NVD·07:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 22, 58202
Event
via FIRST·03:43 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-33539?

CVE-2026-33539 is classified as a critical vulnerability due to its potential for SQL injection and arbitrary code execution.

2

How do I fix CVE-2026-33539?

To fix CVE-2026-33539, upgrade the Parse Server (PostgreSQL adapter) to version 8.6.59 or version 9.6.0-alpha.53 or later.

3

Who is affected by CVE-2026-33539?

CVE-2026-33539 affects users of Parse Server with the PostgreSQL adapter versions lower than 8.6.59 and between 9.0.0 and 9.6.0-alpha.53.

4

What are the exploit conditions for CVE-2026-33539?

An attacker must have master key access to exploit CVE-2026-33539 and inject malicious SQL through field name parameters.

5

What type of vulnerability is CVE-2026-33539?

CVE-2026-33539 is an SQL injection vulnerability that enables attackers to execute arbitrary SQL statements.

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