CVE-2026-34532

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

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.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

Kodem intelligence

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.

1. What is CVE-2026-34532? CVE-2026-34532 is a critical-severity incorrect authorization vulnerability in parse-server (npm), affecting versions >= 9.0.0, < 9.7.0-alpha.11. It is fixed in 9.7.0-alpha.11, 8.6.67. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. Which versions of parse-server are affected by CVE-2026-34532? parse-server (npm) versions >= 9.0.0, < 9.7.0-alpha.11 is affected.
3. Is there a fix for CVE-2026-34532? Yes. CVE-2026-34532 is fixed in 9.7.0-alpha.11, 8.6.67. Upgrade to this version or later.
4. Is CVE-2026-34532 exploitable, and should I be worried? Whether CVE-2026-34532 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2026-34532 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2026-34532?
   • Upgrade parse-server to 9.7.0-alpha.11 or later
   • Upgrade parse-server to 8.6.67 or later