CVE-2026-100631: Improper Neutralization of Special Elements in Data Query Logic in parse-community parse-server
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.
AI Analysis
Technical Summary
CVE-2026-100631 affects parse-community's parse-server in versions prior to 8.6.90 and from 9.0.0 up to 9.10.1-alpha.9. The vulnerability arises from improper validation of client-supplied installation fields used in device token deduplication queries. An unauthenticated attacker knowing only the public application ID can inject query operators via non-string values, causing the deduplication cleanup process—which executes with elevated privileges before class-level permissions are enforced—to delete all or attacker-chosen subsets of device registrations. This deletion is irreversible on the server side, resulting in loss of push notification capability until clients re-register. The vulnerability is remediated in versions 8.6.90 and 9.10.1-alpha.9 by rejecting non-string values with client errors and limiting deduplication scope to the calling application. The default configuration exposing the REST API to clients and using push notifications is affected. No workaround other than upgrading is provided.
Potential Impact
An unauthenticated remote attacker can cause deletion of all or a subset of device registrations for a parse-server application by exploiting this vulnerability. This results in permanent loss of device registration data on the server, disabling push notifications until clients re-register. The attack requires only knowledge of the public application ID and no authentication or user interaction. This can disrupt service availability for push notifications and impact user experience.
Mitigation Recommendations
Upgrade parse-server to version 8.6.90 or later if using the 0.x series, or to version 9.10.1-alpha.9 or later if using the 9.x series. These versions reject non-string values in installation fields and scope deduplication cleanup to the calling application, mitigating the vulnerability. No other workaround is available.
CVE-2026-100631: Improper Neutralization of Special Elements in Data Query Logic in parse-community parse-server
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.
CVSS v4.0
Score 8.7high
Affected software
parse-community
parse-server
parse-community
parse-server
pkg:github/parse-community/parse-serverRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-100631 affects parse-community's parse-server in versions prior to 8.6.90 and from 9.0.0 up to 9.10.1-alpha.9. The vulnerability arises from improper validation of client-supplied installation fields used in device token deduplication queries. An unauthenticated attacker knowing only the public application ID can inject query operators via non-string values, causing the deduplication cleanup process—which executes with elevated privileges before class-level permissions are enforced—to delete all or attacker-chosen subsets of device registrations. This deletion is irreversible on the server side, resulting in loss of push notification capability until clients re-register. The vulnerability is remediated in versions 8.6.90 and 9.10.1-alpha.9 by rejecting non-string values with client errors and limiting deduplication scope to the calling application. The default configuration exposing the REST API to clients and using push notifications is affected. No workaround other than upgrading is provided.
Potential Impact
An unauthenticated remote attacker can cause deletion of all or a subset of device registrations for a parse-server application by exploiting this vulnerability. This results in permanent loss of device registration data on the server, disabling push notifications until clients re-register. The attack requires only knowledge of the public application ID and no authentication or user interaction. This can disrupt service availability for push notifications and impact user experience.
Mitigation Recommendations
Upgrade parse-server to version 8.6.90 or later if using the 0.x series, or to version 9.10.1-alpha.9 or later if using the 9.x series. These versions reject non-string values in installation fields and scope deduplication cleanup to the calling application, mitigating the vulnerability. No other workaround is available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-09-26T02:31:42.100Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ab7c9a5f7a7c5410652fd1a
Added to database: 09/26/2026, 13:33:25 UTC
Last enriched: 09/26/2026, 14:17:48 UTC
Last updated: 09/27/2026, 01:57:11 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.