CVE-2026-34532: Parse Server: Cloud function validator bypass via prototype chain traversal
Impact
An attacker can bypass Cloud Function validator access controls by appending .prototype.constructor to the function name in the URL. When a Cloud Function handler is declared using the function keyword and its validator is a plain object or arrow function, the trigger store traversal resolves the handler through its own prototype chain while the validator store fails to mirror this traversal, causing all access control enforcement to be skipped.
This allows unauthenticated callers to invoke Cloud Functions that are meant to be protected by validators such as requireUser, requireMaster, or custom validation logic.
Patches
The trigger store traversal now verifies that each intermediate node is a legitimate store object before continuing traversal. If the traversal encounters a non-store value such as a function handler, it stops and returns an empty store, preventing prototype chain escape.
Workarounds
Use arrow functions instead of the function keyword for Cloud Function handlers. Arrow functions do not have a prototype property and are not affected by this vulnerability.
Resources
- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-vpj2-qq7w-5qq6 - Fix Parse Server 9: https://github.com/parse-community/parse-server/pull/10342 - Fix Parse Server 8: https://github.com/parse-community/parse-server/pull/10343
Other sources
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.67 and 9.7.0-alpha.11, an attacker can bypass Cloud Function validator access controls by appending "prototype.constructor" to the function name in the URL. When a Cloud Function handler is declared using the function keyword and its validator is a plain object or arrow function, the trigger store traversal resolves the handler through its own prototype chain while the validator store fails to mirror this traversal, causing all access control enforcement to be skipped. This allows unauthenticated callers to invoke Cloud Functions that are meant to be protected by validators such as requireUser, requireMaster, or custom validation logic. This issue has been patched in versions 8.6.67 and 9.7.0-alpha.11.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/parse-serverto a version that resolves this vulnerability.Fixed in 8.6.67 - Upgrade
Upgrade
npm/parse-serverto a version that resolves this vulnerability.Fixed in 9.7.0-alpha.11 - Upgrade
Upgrade
Parse Serverto a version that resolves this vulnerability.Fixed in 8.6.67 - Upgrade
Upgrade
Parse Serverto a version that resolves this vulnerability.Fixed in 9.7.0-alpha.11 - Configuration
Update Cloud Function handlers to be declared as arrow functions (e.g., `const handler = async (...) => { ... }`) to avoid `prototype`-based traversal; this is specifically recommended as a workaround when using the `function` keyword.
Parse Server Cloud Function handlers function keyword vs arrow functions for Cloud Function handlers = Use arrow functions instead of the `function` keyword
Event History
Frequently Asked Questions
What is the severity of CVE-2026-34532?
CVE-2026-34532 has been rated as a medium severity vulnerability.
How do I fix CVE-2026-34532?
To fix CVE-2026-34532, upgrade to Parse Server version 8.6.67 or 9.7.0-alpha.11 or later.
What type of attack does CVE-2026-34532 involve?
CVE-2026-34532 involves a prototype chain traversal attack that allows bypassing Cloud Function validator access controls.
Which versions of Parse Server are affected by CVE-2026-34532?
CVE-2026-34532 affects Parse Server versions prior to 8.6.67 and 9.7.0-alpha.11.
What is the impact of CVE-2026-34532 vulnerability?
The impact of CVE-2026-34532 allows unauthorized access to Cloud Functions, potentially leading to data manipulation.