Parse Server denial of service via beforeSave trigger
Only affects Parse Server 2.5.0 before 8.6.121 and 9.0.0 before 9.11.1-alpha.1, on classes with a beforeSave trigger. Fixed in 8.6.121 and 9.11.1-alpha.1.
- Exploited
- No known exploitation
- Fix
- Fixed in 9.11.1-alpha.1, 8.6.121
- Who is exposed
- Not reported
Summary
Parse Server has a flaw that lets a remote attacker, without logging in, crash the server process and deny service to all clients. The attacker does this by updating an object in a class that has a beforeSave trigger and sending a dot notation key below a non-object field, such as a timestamp.
Written by a model
Original description
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.
Who should check
Teams running parse-server 8.x or 9.x (npm) with beforeSave triggers on classes that clients can update, including user classes
“Parse Server 2.5.0 before 8.6.121 and 9.0.0 before 9.11.1-alpha.1”
What to do
Upgrade to a fixed version: 9.11.1-alpha.1, 8.6.121.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134242 (Parse Server 2.5.0 before 8.6.121 and 9.0.0 before 9.11.1-alpha.1 Denial of Service via beforeSave Trigger), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-134242 (entry last updated 2026-11-21):
Affected:
- npm package parse-server: from 9.0.0, fixed in 9.11.1-alpha.1
- npm package parse-server: from 2.5.0, fixed in 8.6.121
Fixed versions: 9.11.1-alpha.1, 8.6.121.
Conditions (all must be true for the bug to be hit):
- Parse Server 2.5.0 up to 8.6.121, or 9.0.0 up to 9.11.1-alpha.1 (source: https://www.vulncheck.com/advisories/parse-server-2.5.0-before-8.6.121-and-9.0.0-before-9.11.1-alpha.1-denial-of-service-via-beforesave-trigger)
- The affected class has a beforeSave trigger (source: https://github.com/parse-community/parse-server/security/advisories/GHSA-2rxj-6v32-2v6j)
- The object is writable by the client (client key, or a signed-up user on their own user object) (source: https://github.com/parse-community/parse-server/security/advisories/GHSA-2rxj-6v32-2v6j)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-134242 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134242 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/parse-community/parse-server/security/advisories/GHSA-2rxj-6v32-2v6j
- https://www.vulncheck.com/advisories/parse-server-2.5.0-before-8.6.121-and-9.0.0-before-9.11.1-alpha.1-denial-of-service-via-beforesave-trigger
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-134242
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134242"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach10/20Affects npm packages
- Severity8.2/10CVSS 8.2
- No patch0/5No signal
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 40 if advisories confirm default setups are exposed
Impact
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · parse-community/parse-server · Advisory GHSA-2rxj-6v32-2v6j |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134242 |
| Record | NVD · CVE-2026-134242 |
| Other links 1 | |
| Link | vulncheck.com · advisories/parse-server-2.5.0-before-8.6.121-and-9.0.0-before-9.11.1-alpha.1-denial-of-service-via-beforesave-trigger |
Questions about CVE-2026-134242
Is CVE-2026-134242 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
Parse Server does not handle a failure to serialize an object. This can terminate the Parse Server process, causing a denial of service for all clients until the server restarts.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-134242?
parse-server (npm): from 9.0.0 before 9.11.1-alpha.1. parse-server (npm): from 2.5.0 before 8.6.121.
Source: cve.now feed data
Am I affected, and how do I check?
Parse Server 2.5.0 up to 8.6.121, and 9.0.0 up to 9.11.1-alpha.1. Only classes with a beforeSave trigger are affected, and the issue applies when the object is writable by the client key or by a signed-up user on their own user object. The installed version can be checked in the project's package.json or with the parse-server package version.
Source: vulncheck.com, github.com
How do I fix CVE-2026-134242?
Upgrade to 8.6.121 or 9.11.1-alpha.1, the fixed versions for each release line.
Source: vulncheck.com, github.com
Related
- CVE-2026-57480Parse Server: Denial of service via exponential-time processing of deeply nested query operators
- CVE-2026-47138Parse Server: Pre-authentication denial of service via client version header regex backtracking
- CVE-2021-47987Parse Server - Arbitrary Code Execution via Malicious Version Tags
- CVE-2021-47986Parse Server - Unreviewed Code Execution via Malicious Version Tags
- CVE-2026-53726Parse Server: Relation `$relatedTo` query bypasses `protectedFields` and owning-object ACL
- CVE-2026-50008Parse Server: Server option routeAllowList is bypassable through batch sub-requests
No corrections so far. Something wrong on this page? Report an error.