CVE-2026-30962: Parse Server Protected Fields Bypass Vulnerability

parse-server Updated 13 Mar 2026

Summary

11/03/2026
Yes i
High
7.1

CVE-2026-30962: Parse Server has a protected fields bypass via logical query operators. Affects parse-server across 2 version ranges.

< 8.6.19 >= 9.0.0, < 9.5.2-alpha.6

Fixed in 8.6.19 or 9.5.2-alpha.6, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2026-30962 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 with a robust server-side infrastructure. It provides features such as data storage, user authentication, and real-time notifications. However, it has a vulnerability that allows authenticated users to bypass protections on sensitive fields, potentially exposing confidential data.

Vulnerability Detail

The vulnerability arises from inadequate validation of protected fields in Parse Server. The system only checks top-level query keys, allowing attackers to exploit logical operators to access protected fields. This flaw can lead to unauthorized data exposure, as any authenticated user can manipulate queries to retrieve sensitive information.

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.19 8.6.19
    npm install parse-server@8.6.19
  • >= 9.0.0, < 9.5.2-alpha.6 9.5.2-alpha.6
    npm install parse-server@9.5.2-alpha.6

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 a 'beforeFind' trigger in your Parse Server application to manually inspect queries for references to protected fields within logical operators. Here is an example of how to set up this trigger:

Parse.Cloud.beforeFind('YourClassName', async (request) => {
  const query = request.query;
  // Inspect the query for protected fields
  if (query.containsProtectedField()) {
    throw new Parse.Error(Parse.Error.OPERATION_FORBIDDEN, 'Access to protected fields is not allowed.');
  }
});

Conclusion

In summary, CVE-2026-30962 is a significant vulnerability in Parse Server that allows unauthorized access to protected fields through logical query operators. It is crucial to update to the latest patched versions or implement workarounds to safeguard sensitive data.

See every vulnerability recorded for parse-server →

Share this vulnerability

FAQ

CVE-2026-30962 is a vulnerability in Parse Server that allows authenticated users to bypass protections on sensitive fields through logical query operators.

If your application uses Parse Server and is vulnerable, authenticated users may gain unauthorized access to sensitive data, leading to potential data breaches.

All versions of Parse Server prior to 9.5.2-alpha.6 and 8.6.19 are affected by this vulnerability.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application using the Vulert playground without any signup.

The CVSS score of this vulnerability is 7.1, indicating a high severity level.

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.19 8.6.19
    npm install parse-server@8.6.19
  • >= 9.0.0, < 9.5.2-alpha.6 9.5.2-alpha.6
    npm install parse-server@9.5.2-alpha.6

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