Skip to main content
Menu
CVEs

Parse Server authorization bypass in beforeSave via dot notation

CVE-2026-134243Published November 21, 2026, updated

2.3LowCNA
Exploited
No known exploitation
Fix
Fixed in 9.11.1-alpha.2, 8.6.122
Who is exposed
Specific setups only

Summary

Parse Server (parse-community) has a flaw where dot notation keys can change a field that a beforeSave trigger was meant to keep constant or revert, including Object, Array, GeoPoint, Polygon, Bytes (on MongoDB), and ACL fields. A remote client that has login access and permission to write the object can use this to modify such a field, such as a constant role list, and bypass Cloud Code authorization checks.

Written by a model

Original description

Parse Server before 8.6.122 and 9.0.0 before 9.11.1-alpha.2 does not prevent dot notation keys from changing a field that a beforeSave trigger keeps constant or reverts, affecting Object, Array, GeoPoint, Polygon, Bytes (on MongoDB), and ACL fields on create and update. A client allowed to write the object can modify such a field, such as a constant role list, to bypass Cloud Code authorization checks.

Who should check

Teams running parse-server before 8.6.122, or 9.x before 9.11.1-alpha.2, that keep fields constant or revert them in beforeSave triggers for Cloud Code authorization.

“Parse Server before 8.6.122 and 9.0.0 before 9.11.1-alpha.2”

vulncheck.com

What to do

  1. Check whether your setup matches what the bug needs.

    A beforeSave trigger keeps the field constant (constant option of the built-in field validator) or reverts it on the request object. The protected field is of type Object, Array, GeoPoint, Polygon, Bytes (on MongoDB only), or the object's ACL, on create or update.
  2. Upgrade to a fixed version: 9.11.1-alpha.2, 8.6.122.

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-134243 (Parse Server before 8.6.122 and 9.0.0 before 9.11.1-alpha.2 beforeSave Protection Bypass via Dot Notation), 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-134243 (entry last updated 2026-11-21):
Affected:
- npm package parse-server: from 9.0.0, fixed in 9.11.1-alpha.2
- npm package parse-server: fixed in 8.6.122
Fixed versions: 9.11.1-alpha.2, 8.6.122.
Conditions (all must be true for the bug to be hit):
- A beforeSave trigger keeps the field constant (constant option of the built-in field validator) or reverts it on the request object. (source: https://github.com/parse-community/parse-server/security/advisories/GHSA-wq62-rjpm-q29h)
- The protected field is of type Object, Array, GeoPoint, Polygon, Bytes (on MongoDB only), or the object's ACL, on create or update. (source: https://github.com/parse-community/parse-server/security/advisories/GHSA-wq62-rjpm-q29h)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134243 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134243 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-wq62-rjpm-q29h
- https://www.vulncheck.com/advisories/parse-server-before-8.6.122-and-9.0.0-before-9.11.1-alpha.2-beforesave-protection-bypass-via-dot-notation
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-134243
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-134243"}.

Affected versions

cve.now Index

20Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects npm packages
  • Severity2.3/10CVSS 2.3
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 27 if CISA's SSVC rates it automatable

Impact

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

Questions about CVE-2026-134243

Is CVE-2026-134243 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?

A beforeSave trigger that keeps a field unchanged, either with the constant option of the built-in field validator or by reverting the field on the request object, can be bypassed using dot notation. A client that may write the object can then change a field Cloud Code relies on for authorization, such as a constant role list, and gain access the app meant to deny.

Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-134243?

parse-server (npm): from 9.0.0 before 9.11.1-alpha.2. parse-server (npm): before 8.6.122.

Source: cve.now feed data

Am I affected, and how do I check?

Parse Server 9.0.0 before 9.11.1-alpha.2 and versions before 8.6.122 are affected. The bug applies to fields of type Object, Array, GeoPoint, Polygon, Bytes (on MongoDB only), or the object's ACL, on create and update. To check your version, run the server's package version, for example with npm list parse-server.

Source: github.com, vulncheck.com

How do I fix CVE-2026-134243?

Upgrade to Parse Server 8.6.122 or 9.11.1-alpha.2, the fixed versions listed in the advisory. The advisory names no patch identifiers.

Source: github.com, vulncheck.com

No corrections so far. Something wrong on this page? Report an error.