CVE-2026-32234: SQL Injection Vulnerability in Parse Server via Query Field Name
Summary
CVE-2026-32234: Parse Server has a SQL injection via query field name when using PostgreSQL. Affects parse-server across 2 version ranges.
< 8.6.36
>= 9.0.0, < 9.6.0-alpha.10
Fixed in 8.6.36 or 9.6.0-alpha.10, depending on the release line you run. How to fix ↓
Also tracked for
- parse · Bitnami
The same CVE-2026-32234 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
Parse Server is an open-source backend framework that enables developers to build applications with a robust server-side infrastructure. It provides features such as data storage, user authentication, and real-time notifications. However, when configured with PostgreSQL, it is susceptible to a SQL injection vulnerability that can be exploited by attackers with access to the master key.
Vulnerability Detail
The vulnerability arises from the way Parse Server handles field names in query constraints when using PostgreSQL. Specifically, the field name in a $regex query operator is passed to PostgreSQL using unparameterized string interpolation. This allows attackers to inject malicious SQL code, bypassing the Parse Server abstraction layer and directly manipulating the database. The impact of this vulnerability is significant, as it can lead to unauthorized data access or manipulation.
How To Fix
Latest published version: 9.10.5 as of 22 Oct 2026
npm install parse-server@9.10.5Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 8.6.368.6.36npm install parse-server@8.6.36 -
>= 9.0.0, < 9.6.0-alpha.109.6.0-alpha.10npm install parse-server@9.6.0-alpha.10
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
Currently, there are no known workarounds for this vulnerability. The best course of action is to update to the patched versions mentioned above.
Conclusion
The SQL injection vulnerability in Parse Server when using PostgreSQL poses a significant risk to applications that utilize this framework. It is crucial for developers to update to the latest patched versions to mitigate this risk and protect their data integrity.
See every vulnerability recorded for parse-server →
FAQ
The vulnerability is a SQL injection that allows attackers to manipulate SQL queries via crafted field names in query constraints.
Only Parse Server deployments using PostgreSQL are affected by this vulnerability.
Exploitation of this vulnerability can lead to unauthorized access to sensitive data or manipulation of the database.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
The CVSS score for this vulnerability is 5.1, indicating a moderate level of severity.
Related vulnerabilities
Recent vulnerabilities recorded for parse-server.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
