CVE-2026-30966
published 2026-03-10CVE-2026-30966: Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.5.2-alpha.7 and 8.6.20, Parse Server's…
PriorityP268critical10CVSS 3.1
AVNACLPRNUINSCCHIHAL
EPSS
0.38%
30.2th percentile
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.5.2-alpha.7 and 8.6.20, 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. This vulnerability is fixed in 9.5.2-alpha.7 and 8.6.20.
Affected
7 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| parse-community | parse-server | < 8.6.20 | 8.6.20 |
| parse-community | parse-server | — | — |
| parse-community | parse-server | >= 0 < 8.6.20 | 8.6.20 |
| parse-community | parse-server | >= 9.0.0-alpha.1 < 9.5.2-alpha.7 | 9.5.2-alpha.7 |
| parseplatform | parse-server | < 8.6.20 | 8.6.20 |
| parseplatform | parse-server | — | — |
| parseplatform | parse-server | >= 9.0.0 < 9.5.2 | 9.5.2 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Parse Server has role escalation and CLP bypass via direct `_Join` table write
osv·2026-03-11
CVE-2026-30966 [CRITICAL] Parse Server has role escalation and CLP bypass via direct `_Join` table write
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 blo
GHSA
Parse Server has role escalation and CLP bypass via direct `_Join` table write
ghsa·2026-03-11
CVE-2026-30966 [CRITICAL] CWE-284 Parse Server has role escalation and CLP bypass via direct `_Join` table write
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 blo
No detection rules found.
No public exploits indexed.
2026-03-10
Published