CVE-2026-134242 in Parse Serverinfo

Summary

by MITRE • 11/21/2026

Parse Server 2.5.0 before 8.6.121 and 9.0.0 before 9.11.1-alpha.1 does not handle a failure to serialize an object after a beforeSave trigger, leaving the request unsettled and terminating the server process. A remote attacker able to update an object in a class with a beforeSave trigger can send a dot notation key below a non-object field, such as a timestamp, to crash the server for all clients.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Analysis

by VulDB Data Team • 11/21/2026

Parse Server versions 2.5.0 through 8.6.121 and 9.0.0 through 9.11.1-alpha.1 contain a critical stability vulnerability related to improper error handling during object serialization within the beforeSave trigger lifecycle. The core technical flaw arises when an application developer implements a beforeSave hook that attempts to modify or validate fields, but fails to properly serialize the resulting object state back into the database transaction. Specifically, if the server encounters a failure while serializing the modified object, it does not gracefully handle this exception. Instead of rolling back the request and returning an appropriate error code to the client, the internal process leaves the HTTP request in an unsettled state. This unhandled exception propagates up through the Node.js event loop without being caught by standard error handlers, ultimately causing the entire server process to terminate abruptly.

The operational impact of this vulnerability is severe due to its potential for denial-of-service attacks against Parse Server deployments. A remote attacker who possesses write permissions to any class configured with a beforeSave trigger can exploit this flaw. By crafting a specific request that includes dot notation keys targeting non-object fields, such as attempting to set a property on a timestamp or string field where object nesting is not supported, the server attempts an invalid serialization operation. This triggers the unhandled exception path described above. Because Parse Server typically runs in a single-threaded event loop model common to Node.js applications, the termination of one process instance results in immediate service disruption for all connected clients until the server is manually restarted or auto-restarted by a supervisor daemon. In environments without robust health checks and automatic restart mechanisms, this leads to prolonged downtime and loss of availability.

From a classification perspective, this vulnerability aligns with CWE-754: Improper Check for Unusual or Exceptional Conditions, as the software fails to validate whether an operation will succeed before attempting it, leading to a crash when expectations are not met. It also relates to CWE-248: Unhandled Exception, which describes failures in error handling that result in system instability. In terms of offensive security frameworks, this behavior is consistent with ATT&CK technique T1499: Endpoint Denial of Service, specifically under the sub-category of resource exhaustion via application crash. The attack vector requires network access and valid credentials or permissions to write to a targeted class, placing it at a medium complexity level for exploitation but high impact due to total service unavailability.

Mitigation strategies should focus on both immediate patching and architectural resilience. The primary remediation is to upgrade Parse Server to version 8.6.122 or later, where the serialization error handling has been corrected to properly catch exceptions and return appropriate HTTP errors rather than crashing the process. For organizations unable to immediately patch, implementing a reverse proxy such as Nginx with strict timeout settings can help mitigate some effects by resetting stalled connections, though this does not prevent the server crash itself. Deploying multiple instances of Parse Server behind a load balancer is recommended; while one instance may crash due to an exploit attempt, other healthy instances can continue serving traffic, maintaining partial availability. Additionally, developers should review all beforeSave triggers for robust error handling and avoid relying on implicit type coercion that might lead to serialization failures when manipulating nested properties on primitive data types.

Responsible

VulnCheck

Reservation

11/21/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you know our Splunk app?

Download it now for free!