Advisory

GHSA-vpj2-qq7w-5qq6

Also known as: BIT-parse-2026-34532, CVE-2026-34532

Summary

parse-server has cloud function validator bypass via prototype chain traversal

Details

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

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2026-03-31 23:48 UTC
Modified
2026-04-06 15:27 UTC

Affected packages and fixes

parse-server

npm · All systems

Affected

  • introduced 9.0.0, fixed 9.7.0-alpha.11 (semver)

Fixed versions

9.7.0-alpha.11

Fix

parse-server

npm · All systems

Affected

  • introduced 0, fixed 8.6.67 (semver)

Fixed versions

8.6.67

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences