Monitor vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
10.0

Parse Server allows unauthorized access to internal data through API

CVE-2026-30966 GHSA-5f92-jrq3-28rc
Summary

Parse Server's internal data can be accessed by any client with the application key, allowing an attacker to gain elevated permissions and access to sensitive data. To fix this issue, update to the latest version of Parse Server (9.5.2-alpha.7 or 8.6.20).

What to do
  • Update parse-server to version 9.5.2-alpha.7.
  • Update parse-server to version 8.6.20.
Affected software
VendorProductAffected versionsFix available
parse-server > 9.0.0-alpha.1 , <= 9.5.2-alpha.7 9.5.2-alpha.7
parse-server <= 8.6.20 8.6.20
parseplatform parse-server <= 8.6.20
parseplatform parse-server > 9.0.0 , <= 9.5.2
parseplatform parse-server 9.5.2
parseplatform parse-server 9.5.2
parseplatform parse-server 9.5.2
parseplatform parse-server 9.5.2
parseplatform parse-server 9.5.2
parseplatform parse-server 9.5.2
Original title
Parse Server has role escalation and CLP bypass via direct `_Join` table write
Original description
### 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
nvd CVSS3.1 10.0
Vulnerability type
CWE-284 Improper Access Control
Published: 11 Mar 2026 · Updated: 13 Mar 2026 · First seen: 10 Mar 2026