parse-server
Affected
- introduced
9.0.0-alpha.1, fixed9.5.2-alpha.7(semver)
Fixed versions
9.5.2-alpha.7
Fix
- Fixed version
9.5.2-alpha.7npm install [email protected]
Advisory
Also known as: BIT-parse-2026-30966, CVE-2026-30966
Parse Server has role escalation and CLP bypass via direct _Join table write
Impact
Parse Server's internal tables, which store Relation field mappings such as role memberships, can be directly accessed via the REST API or GraphQL API by any client using only the application key. No master key is required.
An attacker can create, read, update, or delete records in any internal relationship table. Exploiting this allows the attacker to inject themselves into any Parse Role, gaining all permissions associated with that role, including full read, write, and delete access to classes protected by role-based Class-Level Permissions (CLP). Similarly, writing to any such table that backs a Relation field used in a pointerFields CLP bypasses that access control.
Patches
The fix blocks direct client access to internal relationship tables in Parse Server's role security enforcement. All create, find, get, update, and delete operations on these tables now require the master key or maintenance key.
Workarounds
There is no known workaround.
References
Critical Basis: The source's own band: CRITICAL
9.0.0-alpha.1, fixed 9.5.2-alpha.7 (semver)9.5.2-alpha.7
9.5.2-alpha.7npm install [email protected]0, fixed 8.6.20 (semver)8.6.20
8.6.20npm install [email protected]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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0