CVE-2026-100631: Parse Server 9.0.0 Unauthenticated Installation Deletion via Operator Injection

Published Sep 26, 2026
·
Updated

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 Software

1 affected component
Parse Platform Parse Server<8.6.90, >=9.0.0<9.10.1-alpha.9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Parse Server to a version that resolves this vulnerability.

    Fixed in 8.6.90
  2. Upgrade

    Upgrade Parse Server to a version that resolves this vulnerability.

    Fixed in 9.10.1-alpha.9

Event History

Sep 26, 2026
CVE Published
via MITRE·01:23 PM
Data Sourced
via MITRE·01:23 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:16 PM
DescriptionSeverityWeakness
Apr 17, 58707
Event
via NVD·06:18 PM

Frequently Asked Questions

1

Which deployments are realistically exposed?

Any affected deployment that exposes the REST API to clients and uses push notifications is affected in its default configuration. An attacker only needs the public application ID.

2

What access or interaction does an attacker need?

None beyond network access to the REST API and knowledge of the public application ID. No account, session token, master key, or user interaction is required.

3

What is the operational impact if exploitation succeeds?

The attacker can delete all device registrations for an application or an attacker-chosen subset. The deleted registrations cannot be recovered on the server, and push notifications will fail until clients register again.

4

What should teams do if they cannot patch immediately?

No workaround other than upgrading is available. Upgrade to 8.6.90 or 9.10.1-alpha.9, which reject non-string installation field values and scope cleanup to the calling application.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203