CVE-2026-32234

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

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.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

Kodem intelligence

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.

1. What is CVE-2026-32234? CVE-2026-32234 is a medium-severity SQL injection vulnerability in parse-server (npm), affecting versions >= 9.0.0, < 9.6.0-alpha.10. It is fixed in 9.6.0-alpha.10, 8.6.36. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
2. Which versions of parse-server are affected by CVE-2026-32234? parse-server (npm) versions >= 9.0.0, < 9.6.0-alpha.10 is affected.
3. Is there a fix for CVE-2026-32234? Yes. CVE-2026-32234 is fixed in 9.6.0-alpha.10, 8.6.36. Upgrade to this version or later.
4. Is CVE-2026-32234 exploitable, and should I be worried? Whether CVE-2026-32234 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2026-32234 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2026-32234?
   • Upgrade parse-server to 9.6.0-alpha.10 or later
   • Upgrade parse-server to 8.6.36 or later

Other vulnerabilities in parse-server