CVE-2026-32594: Parse Server GraphQL WebSocket Endpoint Security Bypass

parse Updated 20 Mar 2026

Summary

20/03/2026
Yes i
Medium
Not published

CVE-2026-32594: Parse Server GraphQL WebSocket endpoint bypasses security middleware. Affects parse across 2 version ranges.

< 8.6.40 >= 9.0.0, < 9.6.0

Fixed in 8.6.40 or 9.6.0, depending on the release line you run. How to fix ↓

Also tracked for

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.

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Parse Server is an open-source backend platform that allows developers to build applications with a robust server-side infrastructure. It supports various features such as data storage, user authentication, and real-time notifications. The platform can be deployed on any infrastructure that supports Node.js, making it versatile for developers. However, it has a vulnerability in its GraphQL WebSocket endpoint that can be exploited if not properly secured.

Vulnerability Detail

The vulnerability arises from the GraphQL WebSocket endpoint for subscriptions in Parse Server versions prior to 8.6.40 and 9.6.0. This endpoint does not pass requests through the Express middleware chain, which is responsible for enforcing authentication, introspection control, and query complexity limits. As a result, an attacker can connect to the WebSocket endpoint without a valid application or API key, access the GraphQL schema even when public introspection is disabled, and send complex queries that bypass configured limits. This could lead to unauthorized data access and potential denial of service due to resource exhaustion.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 8.6.40 8.6.40
  • >= 9.0.0, < 9.6.0 9.6.0

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 workaround, you can restrict access to the WebSocket endpoint by implementing additional network-level security measures, such as firewall rules or VPN access, until you can update to a secure version.

Conclusion

CVE-2026-32594 represents a significant security risk for applications using Parse Server versions prior to 8.6.40 and 9.6.0. It is crucial for developers to update their installations to the latest versions to mitigate this vulnerability and protect their applications from potential exploitation.

See every vulnerability recorded for parse →

Share this vulnerability

FAQ

CVE-2026-32594 is a vulnerability in Parse Server that allows unauthorized access to the GraphQL WebSocket endpoint, bypassing security middleware.

Versions prior to 8.6.40 and 9.6.0 are affected by this vulnerability.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

The risks include unauthorized access to sensitive data, execution of complex queries that could lead to denial of service, and exposure of the GraphQL schema.

If you cannot update immediately, implement network-level security measures to restrict access to the WebSocket endpoint as a temporary workaround.

Related vulnerabilities

Recent vulnerabilities recorded for parse.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 8.6.40 8.6.40
  • >= 9.0.0, < 9.6.0 9.6.0

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback