Advisory

GHSA-5f92-jrq3-28rc

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

Summary

Parse Server has role escalation and CLP bypass via direct _Join table write

Details

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

  • GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-5f92-jrq3-28rc
  • Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.2-alpha.7
  • Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.20

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2026-03-11 00:21 UTC
Modified
2026-03-14 03:41 UTC

Affected packages and fixes

parse-server

npm · All systems

Affected

  • introduced 9.0.0-alpha.1, fixed 9.5.2-alpha.7 (semver)

Fixed versions

9.5.2-alpha.7

Fix

parse-server

npm · All systems

Affected

  • introduced 0, fixed 8.6.20 (semver)

Fixed versions

8.6.20

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