Threats Tagged 'cve-2026-100631'
View all threats tagged with 'cve-2026-100631'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2026-100631'
Click on any threat for detailed analysis and mitigation recommendations
Parse Server versions prior to 8.6.90 and from 9.0.0 prior to 9.10.1-alpha.9 contain a vulnerability in the device token deduplication logic. This logic fails to validate the type of client-supplied installation fields before using them in database queries. An unauthenticated attacker knowing only the public application ID can inject query operators to cause deletion of device registrations. This deletion disrupts push notifications until clients re-register. The issue is fixed in versions 8.6.90 and 9.10.1-alpha.9 by rejecting non-string values and scoping cleanup to the calling application. No workaround other than upgrading is available. Join the discussion | GCVE Database | 09/26/2026, 15:31:16 UTC Added: 09/27/2026, 04:30:30 UTC |
0 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. Join the discussion | CVE Database V5 | 09/26/2026, 13:23:07 UTC Added: 09/26/2026, 13:33:25 UTC |
Showing 1 to 2 of 2 results