CVE-2026-109301: Parse Server before 8.6.95 and 9.0.0 before 9.10.2-alpha.3 Denial of Service via File Pointer Without URL

Published Oct 12, 2026
·
Updated

Parse Server before 8.6.95 and 9.0.0 before 9.10.2-alpha.3 does not resolve file references lacking a URL before passing objects to Cloud Code triggers and LiveQuery, causing an uncaught exception that terminates the process. Attackers able to write to a class with Cloud Code save, find, or delete triggers or LiveQuery enabled, including unauthenticated users when public write access or sign-up is allowed, can crash the server or break subsequent requests.

Affected Software

1 affected component
Parse Parse Server<8.6.95, >=9.0.0<9.10.2-alpha.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Parse Server to a version that resolves this vulnerability.

    Fixed in 8.6.95
  2. Upgrade

    Upgrade Parse Server to a version that resolves this vulnerability.

    Fixed in 9.10.2-alpha.3

Event History

Oct 12, 2026
CVE Published
via MITRE·04:04 PM
Data Sourced
via MITRE·04:04 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to unauthenticated denial-of-service?

Deployments are exposed without authentication when an affected class permits public writes or user sign-up is allowed, and that class has Cloud Code save, find, or delete triggers or LiveQuery enabled. Other affected deployments require an attacker to be able to write to such a class.

2

What configuration makes a writable class susceptible?

The class must have Cloud Code save, find, or delete triggers configured, or have LiveQuery enabled. A file reference lacking a URL can then reach those components and cause an uncaught exception.

3

What is the practical impact of successful exploitation?

Successful exploitation can terminate the Parse Server process. It can also cause subsequent requests to fail.

4

What can be done before updating?

Restrict write access to classes that use Cloud Code save, find, or delete triggers or LiveQuery, and disable public writes or unrestricted sign-up where those paths are exposed. These measures reduce the ability of an unauthenticated attacker to submit the triggering object.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203