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

parse Updated 19 Oct 2026

Summary

19/10/2026
Yes i
Medium
Not published

CVE-2026-109303: Parse Server before 8.6.93 and 9.0.0 before 9.10.1 protectedFields Bypass via Relation Count Query. Affects parse across 2 version ranges.

< 8.6.93 >= 9.0.0, < 9.10.1

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

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

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile 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 provides a robust framework for building applications. It offers features such as data storage, user authentication, and real-time notifications. However, certain versions of Parse Server are vulnerable to a bypass of protected fields, which can expose sensitive information to authenticated users.

Vulnerability Detail

The vulnerability arises in Parse Server versions prior to 8.6.93 and 9.0.0 before 9.10.1, where the enforcement of identity-scoped protected fields is not applied on count queries using the $relatedTo operator. This oversight allows authenticated users to exploit the system by combining count queries with objectId constraints, thereby revealing confidential memberships such as private groups or block lists. The potential ramifications include unauthorized access to sensitive data, which could lead to privacy breaches and data leaks.

How To Fix

Fixed versions by release line

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

  • < 8.6.93 8.6.93
  • >= 9.0.0, < 9.10.1 9.10.1

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, consider restricting access to sensitive data by implementing additional checks in your application logic to prevent unauthorized users from executing count queries on protected fields.

Conclusion

CVE-2026-109303 represents a significant security risk for users of Parse Server versions prior to the patched releases. It is crucial to update to the latest versions to safeguard sensitive data and maintain the integrity of your applications.

See every vulnerability recorded for parse →

Share this vulnerability

FAQ

CVE-2026-109303 is a vulnerability in Parse Server that allows authenticated users to bypass protections on sensitive data through count queries.

Parse Server versions before 8.6.93 and 9.0.0 before 9.10.1 are affected by this vulnerability.

The risks include unauthorized access to confidential memberships and potential privacy breaches.

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

If an immediate update is not possible, implement additional access controls in your application to mitigate the risk of unauthorized data exposure.

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.93 8.6.93
  • >= 9.0.0, < 9.10.1 9.10.1

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