CVE-2026-32234: Parse Server has a SQL injection via query field name when using PostgreSQL

Published Mar 11, 2026
·
Updated

Impact

An attacker with access to the master key can inject malicious SQL via crafted field names used in query constraints when Parse Server is configured with PostgreSQL as the database. The field name in a $regex query operator is passed to PostgreSQL using unparameterized string interpolation, allowing the attacker to manipulate the SQL query. While the master key controls what can be done through the Parse Server abstraction layer, this SQL injection bypasses Parse Server entirely and operates at the database level.

This vulnerability only affects Parse Server deployments using PostgreSQL.

Patches

The fix applies proper SQL identifier escaping to field names in the query handler and hardens query field name validation to reject malicious field names for all query types.

Workarounds

There is no known workaround.

References

- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-c442-97qw-j6c6 - Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.10 - Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.36

Other sources

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.6.0-alpha.10 and 8.6.36, an attacker with access to the master key can inject malicious SQL via crafted field names used in query constraints when Parse Server is configured with PostgreSQL as the database. The field name in a $regex query operator is passed to PostgreSQL using unparameterized string interpolation, allowing the attacker to manipulate the SQL query. While the master key controls what can be done through the Parse Server abstraction layer, this SQL injection bypasses Parse Server entirely and operates at the database level. This vulnerability only affects Parse Server deployments using PostgreSQL. This vulnerability is fixed in 9.6.0-alpha.10 and 8.6.36.

MITRE

Affected Software

15 affected componentsFixes available
npm/parse-server<8.6.36
npm/parse-server<9.6.0-alpha.10
npm/parse-server<8.6.36
8.6.36
npm/parse-server>=9.0.0<9.6.0-alpha.10
9.6.0-alpha.10
parseplatform Parse-server Node.js<8.6.36
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-alpha2
parseplatform Parse-server Node.js=9.6.0-alpha3
parseplatform Parse-server Node.js=9.6.0-alpha4
parseplatform Parse-server Node.js=9.6.0-alpha5
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 11, 2026
CVE Published
via MITRE·07:58 PM
Data Sourced
via MITRE·07:58 PM
DescriptionWeakness
Data Sourced
via NVD·08:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Mar 12, 2026
Advisory Published
via GitHub·04:37 PM
Data Sourced
via GitHub·04:37 PM
DescriptionWeaknessAffected Software
Jan 29, 58178
Event
via FIRST·08:09 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-32234?

CVE-2026-32234 is a critical SQL injection vulnerability that affects Parse Server when using PostgreSQL.

2

How do I fix CVE-2026-32234?

To remediate CVE-2026-32234, upgrade Parse Server to version 8.6.36 or 9.6.0-alpha.10 or higher.

3

What are the symptoms of CVE-2026-32234 exploitation?

Exploitation of CVE-2026-32234 may result in unauthorized access to the database and manipulation of data.

4

Who is affected by CVE-2026-32234?

Users running Parse Server versions prior to 8.6.36 or between 9.0.0 and 9.6.0-alpha.10 on PostgreSQL are affected by CVE-2026-32234.

5

What types of attacks are possible with CVE-2026-32234?

CVE-2026-32234 allows attackers to perform SQL injection attacks through crafted field names in query constraints.

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