CVE-2026-32594: Parse Server GraphQL WebSocket Endpoint Security Bypass
Summary
CVE-2026-32594: Parse Server's GraphQL WebSocket endpoint bypasses security middleware. Affects parse-server across 2 version ranges.
< 8.6.40
>= 9.0.0, < 9.6.0-alpha.14
Fixed in 8.6.40 or 9.6.0-alpha.14, depending on the release line you run. How to fix ↓
Also tracked for
- parse · Bitnami
The same CVE-2026-32594 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 a variety of features including data storage, user management, and real-time capabilities through APIs. However, a significant vulnerability has been identified in its GraphQL API, specifically in the WebSocket endpoint for subscriptions, which can lead to unauthorized access and manipulation of data.
Vulnerability Detail
The vulnerability arises from the GraphQL WebSocket endpoint not passing requests through the necessary Express middleware chain that enforces authentication and query complexity limits. This oversight allows attackers to connect to the WebSocket endpoint without valid credentials, execute arbitrary GraphQL operations, and bypass security measures such as introspection control. As a result, sensitive data can be exposed, and the integrity of the application can be compromised.
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.408.6.40npm install parse-server@8.6.40 -
>= 9.0.0, < 9.6.0-alpha.149.6.0-alpha.14npm install parse-server@9.6.0-alpha.14
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
As a temporary measure, block WebSocket upgrade requests to the GraphQL subscriptions path (default: /subscriptions) at the network level. This can be achieved using a reverse proxy or load balancer rule. For example, if using Nginx, you can add the following configuration:
location /subscriptions {
deny all;
}
Conclusion
The vulnerability CVE-2026-32594 in Parse Server's GraphQL WebSocket endpoint poses a significant security risk by allowing unauthorized access and manipulation of data. It is crucial for developers to update their Parse Server installations to the latest patched versions or implement the recommended workarounds to protect their applications.
See every vulnerability recorded for parse-server →
FAQ
The vulnerability allows unauthorized access to the GraphQL WebSocket endpoint, enabling attackers to execute operations without authentication.
You can check if your application is affected by using Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground.
Versions of Parse Server from 0.0.0 up to 9.6.0-alpha.14 are affected. Ensure you are using a patched version.
Yes, the permanent fix is to update to the latest patched version of Parse Server as specified in the 'how to fix' section.
If an immediate update is not possible, implement the suggested workaround to block WebSocket upgrade requests to mitigate the risk.
References
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.
