CVE-2026-33421: Parse Server LiveQuery Bypasses CLP Pointer Permission Enforcement

parse-server Updated 20 Mar 2026

Summary

20/03/2026
Yes i
High
7.1

CVE-2026-33421: Parse Server's LiveQuery bypasses CLP pointer permission enforcement. Affects parse-server across 2 version ranges.

< 8.6.53 >= 9.0.0, < 9.6.0-alpha.42

Fixed in 8.6.53 or 9.6.0-alpha.42, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2026-33421 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Parse Server is an open-source backend framework that enables developers to build applications quickly and efficiently. It provides features such as data storage, user authentication, and real-time updates through its LiveQuery functionality. However, a recent vulnerability has been identified in the LiveQuery WebSocket interface, which fails to enforce Class-Level Permission (CLP) pointer permissions, potentially exposing sensitive data to unauthorized users.

Vulnerability Detail

The vulnerability arises from the LiveQuery interface not enforcing CLP pointer permissions, specifically the 'readUserFields' and 'pointerFields'. This oversight allows any authenticated user to subscribe to LiveQuery events and receive updates for all objects in classes that are supposed to be protected by pointer permissions. As a result, users can access sensitive data that should be restricted, leading to unauthorized data exposure.

How To Fix

Latest published version: 9.10.5 as of 22 Oct 2026

npm install parse-server@9.10.5

Upgrading 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.53 8.6.53
    npm install parse-server@8.6.53
  • >= 9.0.0, < 9.6.0-alpha.42 9.6.0-alpha.42
    npm install parse-server@9.6.0-alpha.42

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, implement Access Control Lists (ACLs) on individual objects to restrict read access instead of solely relying on CLP pointer permissions. This ensures that only authorized users can access specific data.

Conclusion

The vulnerability CVE-2026-33421 in Parse Server's LiveQuery interface poses a significant risk by allowing unauthorized access to sensitive data. It is crucial to update the package to the latest patched version or implement ACLs as a workaround to mitigate this risk.

See every vulnerability recorded for parse-server →

Share this vulnerability

FAQ

The vulnerability allows unauthorized users to access sensitive data through LiveQuery, bypassing intended access controls.

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

CLPs are rules that define which users can read or write to specific fields in a database class, ensuring data security and privacy.

Yes, the permanent fix is to update the 'parse-server' package to the specified patched versions.

If an immediate update is not possible, implement ACLs on individual objects to maintain data security until the package can be updated.

Related vulnerabilities

Recent vulnerabilities recorded for parse-server.

How To Fix

Latest published version: 9.10.5 as of 22 Oct 2026

npm install parse-server@9.10.5

Upgrading 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.53 8.6.53
    npm install parse-server@8.6.53
  • >= 9.0.0, < 9.6.0-alpha.42 9.6.0-alpha.42
    npm install parse-server@9.6.0-alpha.42

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