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

> Unauthenticated attackers can inject query operators to delete all device registrations, disrupting push notifications in Parse Server deployments.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** BIT-parse-2026-100631, GHSA-cc6h-c8m4-hgrx, GHSA-fq69-3pm5-2h3g

## What is CVE-2026-100631?

CVE-2026-100631 is a high-severity code injection vulnerability in parse-community parse-server, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-943 (Improper Neutralization of Special Elements in Data Query Logic)

## Which versions are affected by CVE-2026-100631?

1 open source package ship an affected version, including parse.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `parse` | Bitnami | All versions | 8.6.90, 9.10.1 |

## How do I fix CVE-2026-100631?

Upgrade parse to a fixed version for your release line: 8.6.90 or 9.10.1.

## Is CVE-2026-100631 being exploited?

There is no known exploitation of CVE-2026-100631 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100631 and fix it if it is affected.

What it is: CVE-2026-100631 is a high-severity code injection vulnerability in parse-community parse-server, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-100631 in the wild and no public exploit code.

Affected packages and fixed versions:
- parse (Bitnami): affected all versions; fixed in 8.6.90, 9.10.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100631/ (Markdown: https://insights.sbomify.com/CVE-2026-100631/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100631
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100631
- OSV: https://osv.dev/vulnerability/CVE-2026-100631

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100631/
Summaries are generated and may contain mistakes; the official description above is the record.