CVE-2026-100631
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 27% of all known CVEs.
References
Related Vulnerabilities
Other CWE-943 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2017-12904 | High | 8.8 | 6.4% | - | Fix |
| CVE-2026-27886 | High | 7.5 | 2.5% | - | Fix |
| CVE-2020-36195 | Critical | 9.8 | 1.8% | - | Fix |
| CVE-2018-7829 | High | 8.8 | 1.7% | - | Fix |
| CVE-2022-36084 | Critical | 9.9 | 1.5% | - | Fix |
| CVE-2021-1349 | Medium | 6.5 | 1.4% | - | Fix |
Common questions
How do I fix CVE-2026-100631?
No published fix for CVE-2026-100631 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-100631 being actively exploited?
Not that we know of. CVE-2026-100631 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.36% is the estimated probability that it will be exploited in the next 30 days. That is higher than 27% of all scored CVEs.
How severe is CVE-2026-100631?
CVE-2026-100631 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-100631
Markdown
[](https://tridentstack.com/cve/CVE-2026-100631)HTML
<a href="https://tridentstack.com/cve/CVE-2026-100631"><img src="https://tridentstack.com/cve/badge/CVE-2026-100631.svg" alt="CVE-2026-100631"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-30.