CVE-2026-100631

Parse Server 9.0.0 Unauthenticated Installation Deletion via Operator Injection

HIGH
7.5
CVSS Score
Published: September 26, 2026 at 01:23 PM UTC
Updated: September 30, 2026 at 05:23 PM UTC
2 products affected across 2 vendorsParse ServerParse Server

Using parse-server by parse-community?

Get instant alerts when new vulnerabilities affect parse-server - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

Parse Server is an open source backend server. In versions prior to 8.6.90 and in versions from 9.0.0 prior to 9.10.1-alpha.9, the device token deduplication logic for installation records does not validate the type of client-supplied installation fields before using them to build database queries. An unauthenticated remote attacker who knows only the public application ID can submit non-string values in these fields to inject query operators, causing the deduplication cleanup — which runs with elevated privileges before class-level permissions are evaluated — to delete every device registration in the application or an attacker-chosen subset of them. No account, session token, master key, or user interaction is required. Deleted registrations cannot be recovered on the server, so push notifications cannot be delivered until every client re-registers. Any deployment that exposes the REST API to clients and uses push notifications is affected in its default configuration. Versions 8.6.90 and 9.10.1-alpha.9 fix the issue by rejecting non-string values with a client error and by scoping the deduplication cleanup to the calling application. No workaround other than upgrading is available.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 8.6.909.0.0 ≤ v < 9.10.1-alpha.9
Affected range stops below 8.6.90, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.10.1-alpha.9, so it looks safe — our inference, not a vendor statement
v < 8.6.909.0.0 ≤ v < 9.10.1-alpha.99.0.0
Vendor states this is fixed in 8.6.90 (unaffected)
Vendor states this is fixed in 9.10.1-alpha.9 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHVulnCheck
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-943

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card