CVE-2026-34532: Parse Server: Cloud function validator bypass via prototype chain traversal

Published Mar 31, 2026
·
Updated

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

15 affected componentsFixes available
npm/parse-server<8.6.67, <9.7.0-alpha.11
npm/parse-server<8.6.67
8.6.67
npm/parse-server>=9.0.0<9.7.0-alpha.11
9.7.0-alpha.11
parseplatform Parse-server Node.js<8.6.67
parseplatform Parse-server Node.js>=9.0.0<9.7.0
parseplatform Parse-server Node.js=9.7.0-alpha1
parseplatform Parse-server Node.js=9.7.0-alpha10
parseplatform Parse-server Node.js=9.7.0-alpha2
parseplatform Parse-server Node.js=9.7.0-alpha3
parseplatform Parse-server Node.js=9.7.0-alpha4
parseplatform Parse-server Node.js=9.7.0-alpha5
parseplatform Parse-server Node.js=9.7.0-alpha6
parseplatform Parse-server Node.js=9.7.0-alpha7
parseplatform Parse-server Node.js=9.7.0-alpha8
parseplatform Parse-server Node.js=9.7.0-alpha9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/parse-server to a version that resolves this vulnerability.

    Fixed in 8.6.67
  2. Upgrade

    Upgrade npm/parse-server to a version that resolves this vulnerability.

    Fixed in 9.7.0-alpha.11
  3. Upgrade

    Upgrade Parse Server to a version that resolves this vulnerability.

    Fixed in 8.6.67
  4. Upgrade

    Upgrade Parse Server to a version that resolves this vulnerability.

    Fixed in 9.7.0-alpha.11
  5. 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

Mar 31, 2026
CVE Published
via MITRE·02:42 PM
Data Sourced
via MITRE·02:42 PM
DescriptionWeakness
Data Sourced
via NVD·03:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·11:48 PM
Data Sourced
via GitHub·11:48 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-34532?

CVE-2026-34532 has been rated as a medium severity vulnerability.

2

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.

3

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.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203