Is CVE-2026-100631 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-100631 being exploited in the wild.

How severe is CVE-2026-100631?

High severity, with a CVSS score of 7.5, published 26 September 2026.

Which products and versions are affected?

Parse Community Parse Server <8.6.90 and 9.0.0 to <9.10.1-alpha.9.

Is there a fix for CVE-2026-100631?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-100631 attacked?

It is attacked over the network.

Am I affected by CVE-2026-100631?

Check whether you run Parse Community Parse Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-100631: Parse Server operator injection in device token deduplication

Q: Is there a fix for CVE-2026-100631?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2026-100631 attacked?

It is attacked over the network.

Q: Am I affected by CVE-2026-100631?

Check whether you run Parse Community Parse Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-100631 · Severity: high · CVSS 7.5 · Published 2026-09-26

Parse Server is an open source backend that manages user data and push notifications for mobile and web applications. An unauthenticated attacker can delete all device registrations in an application using ordinary HTTP requests, preventing push notifications from being delivered until clients re-register. Only the application's public ID is needed—no password, session token, or special key is required.

Technologies: Parse Community Parse Server. Vendors: Parse Community.

Quick answers

Is CVE-2026-100631 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-100631 being exploited in the wild.
How severe is CVE-2026-100631?: High severity, with a CVSS score of 7.5, published 26 September 2026.
Which products and versions are affected?: Parse Community Parse Server <8.6.90 and 9.0.0 to <9.10.1-alpha.9.
Is there a fix for CVE-2026-100631?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-100631 attacked?: It is attacked over the network.
Am I affected by CVE-2026-100631?: Check whether you run Parse Community Parse Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The device token deduplication logic for installation records fails to validate that client-supplied fields are strings before using them to build database queries, allowing an attacker to inject query operators. The cleanup runs with elevated privileges before class-level permissions are evaluated, enabling deletion of all registrations or an attacker-chosen subset. The fix validates field types and scopes the deduplication cleanup to the calling application.

Affected products

Parse Community Parse Server <8.6.90 and 9.0.0 to <9.10.1-alpha.9

Timeline

2026-09-26: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.