Skip to main content

Parse Server CVE-2026-116801

| EUVDEUVD-2026-110509 MEDIUM
Improper Neutralization of Special Elements in Data Query Logic (CWE-943)
2026-10-26 VulnCheck GHSA-mfg3-66fp-4xc4
5.3
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as client with read access to owning class
  2. Exploit
    Send $relatedTo query with operator instead of objectId
  3. Impact
    Bypass owning-object ACL check, disclose linked readable objects

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Query language parameterization
Exploitation Conditions

Requires an authenticated client (PR:L) that already holds read access to at least one object of the owning class, and a target class that exposes a Relation field queried via $relatedTo. Exploitation consists of supplying a query operator (non-string value) in place of the owning-object objectId - including when nested inside $or, $and, or $nor - to bypass the owning-object ACL check added for GHSA-wmwx-jr2p-4j4r. Limiting factors: only objects the attacker can already read are returned (so this discloses cross-ACL linkage/relationship membership, not the contents of unreadable owning objects); impact is read-only (no integrity or availability effect); and it is confined to applications that use Relation fields and expose them to query. The workaround is a beforeFind trigger on relation-queried classes that rejects $relatedTo queries whose owning objectId is not a string; the complete fix is updating to a patched version.

Impact

This is a moderate, low-urgency information-disclosure flaw rather than a top priority. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) with vulnerable-system confidentiality only (VC:L, VI:N, VA:N) and a base score of 5.3 describes a network-reachable but authenticated issue with limited, read-only impact - consistent with the description, which requires a client that already has read access to at least one object of the owning class and only leaks the linkage of objects the attacker could already read. The signals align rather than conflict: EPSS is low (0.25%, 17th percentile), the CVE is NOT on CISA KEV, and the CISA SSVC framework records Exploitation: none, Automatable: no, Technical Impact: partial. The vuln.today decision label is 'this_month,' indicating a patch-in-normal-cycle priority, not an emergency. There are no indications of active exploitation or weaponization. In short, this is a legitimate but bounded ACL-bypass/information-disclosure bug (a regression around the owning-object authorization previously added for GHSA-wmwx-jr2p-4j4r), appropriate to remediate on a routine patch cadence rather than as a crisis.

Exploit ScenarioDerived

An authenticated low-privilege client of a Parse Server application that holds read access to at least one object of a class exposing a Relation field sends a $relatedTo relation query in which the owning-object reference is a query operator rather than a concrete objectId. Because the owning-object ACL check is bypassed, the server returns which readable objects are linked to owning objects the attacker is not permitted to read, disclosing relationship/linkage information across ACL boundaries. No public exploit identified at time of analysis; a vendor (VulnCheck) and GHSA advisory describe the mechanism but no verified working exploit code is provided.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 28, 2026

Parse Server's $relatedTo relation query does not validate the owning object reference, so an authenticated client can substitute a query operator for the object ID and slip past the owning-object ACL check introduced for GHSA-wmwx-jr2p-4j4r. The result is a limited information disclosure: the attacker learns which objects they can already read are linked to owning objects they are not permitted to read, in deployments that expose Relation fields to queries. Severity is moderate (CVSS 5.3, PR:L, confidentiality-only), EPSS is low at 0.25% (17th percentile), there is no CISA KEV listing, and no public exploit has been identified at time of analysis.

RemediationAI

Upgrade to a patched release: Parse Server 8.6.105 for the 8.x line (PR https://github.com/parse-community/parse-server/pull/10784) or 9.10.5-alpha.6 for the 9.x line (PR https://github.com/parse-community/parse-server/pull/10783), noting that the 9.x fix is published as a pre-release alpha, so teams tracking stable 9.x should confirm the next stable release containing it before upgrading. Where upgrading is not immediately possible, the vendor workaround is to add a beforeFind trigger to every class queried through a Relation field that rejects $relatedTo queries whose owning objectId is not a string, including when nested in $or, $and or $nor; the cost is extra Cloud Code execution on those query paths and the need to reimplement the check for each relation-backed class, and the trigger must be written carefully or it will itself be bypassed by nested query shapes. The workaround is only a stopgap - the advisory treats the validation added in the patched versions as the complete fix - and because exploitation requires an authenticated client with read access to at least one object of the owning class, restricting Class Level Permissions and reviewing which roles can read relation-bearing classes reduces exposure in the interim. Advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-58m4-cqvw-4vgh.

Affected VersionsENISA

parse-server 9.0.0 <9.10.5-alpha.6
parse-server 0 <8.6.105

Affected Packages

euvd parse_server fix: 8.6.105, 9.10.5-alpha.6

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Parse Server is the open-source Node.js backend for the Parse Platform, exposing a REST/GraphQL API over MongoDB or PostgreSQL where classes carry ACLs and objects can be linked through Relation fields. A relational lookup is expressed with the $relatedTo query constraint, which normally takes an owning object reference (including its objectId) plus a relation key; the server resolves the relation and returns the linked objects. This flaw is CWE-943 (improper neutralization of special elements in data query logic - the NoSQL-injection class): because the owning object reference and relation key are not validated as strings, an attacker can pass a query operator where the objectId is expected, including when nested inside $or, $and or $nor, and the owning-object authorization check is bypassed. The upstream fix in PR #10783 (9.x) and PR #10784 (8.x) validates both the owning object reference and the relation key and rejects queries whose owning reference is not a string. The trigger conditions and the exact operator semantics beyond the non-string rejection are not described in the available sources.

Know when Parse Server gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 5.3 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 4.3 MEDIUM

Network-reachable API but requires an authenticated client with read access to one owning-class object (PR:L); limited read-only disclosure of linkage data gives C:L with no integrity or availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

1
Patch available
Oct 27, 2026 - 01:15 EUVD

DescriptionCVE.org

Parse Server before 8.6.105 and 9.0.0 before 9.10.5-alpha.6 does not validate the owning object reference in $relatedTo relation queries, so supplying a query operator instead of an object ID bypasses the owning-object ACL check. A client with read access to at least one object of the owning class can disclose which readable objects are linked to owning objects it cannot read.

Threat Intelligence Overview

EPSS Score
0.3%
Top 83% exploitable
Prevalence
Medium
popular open-source Node.js backend (BaaS) framework, common but not ubiquitous
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

NoSQL injection exploits databases that don't use traditional SQL syntax-like MongoDB, CouchDB, or Redis-by manipulating queries through unsanitized user input.

CVE-2022-24760 CRITICAL POC
10.0 Mar 12

Parse Server is an open source http web server backend. Rated critical severity (CVSS 10.0), this vulnerability is remot

CVE-2026-32248 CRITICAL POC
9.8 Mar 12

Unauthenticated query injection in Parse Server before 9.6.0-alpha.12/8.6.38. PoC available.

CVE-2026-30965 CRITICAL POC
9.1 Mar 10

Parse Server has an incorrect authorization vulnerability enabling unauthorized data access across applications.

CVE-2026-32242 HIGH POC
7.4 Mar 12

### Impact Parse Server's built-in OAuth2 auth adapter exports a singleton instance that is reused directly across all

CVE-2026-30966 CRITICAL
10.0 Mar 10

Parse Server has a CVSS 10.0 access control vulnerability enabling complete bypass of all data access restrictions.

CVE-2024-27298 CRITICAL
10.0 Mar 01

parse-server is a Parse Server for Node.js / Express. Rated critical severity (CVSS 10.0), this vulnerability is remotel

CVE-2026-30863 CRITICAL
9.8 Mar 07

Authentication bypass in Parse Server allows unauthenticated access to protected API endpoints. Parse Server is a popula

CVE-2026-31840 CRITICAL
9.8 Mar 11

SQL injection in Parse Server before 9.6.0-alpha.2/8.6.28.

CVE-2026-31871 CRITICAL
9.8 Mar 11

SQL injection in Parse Server before 9.6.0-alpha.5/8.6.31. Third Parse Server SQLi.

CVE-2026-31856 CRITICAL
9.8 Mar 11

SQL injection in Parse Server before 9.6.0-alpha.5/8.6.31.

CVE-2023-36475 CRITICAL
9.8 Jun 28

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Rated critical s

CVE-2022-41878 CRITICAL
9.8 Nov 10

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Rated critical s

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy