# CVE-2026-30966: parse-server — Fix Available 📦 📦 npm Not in CISA KEV CRITICAL severity # CVE-2026-30966 — parse-server CRITICAL CVE-2026-30966 is a critical-severity (CVSS 10) CWE-284 vulnerability in parse-server. A fix is available for parse-server — see the affected versions and patch details below. Parse Server role escalation and CLP bypass via direct \`\_Join\` table write Also known asBIT-parse-2026-30966[GHSA-5f92-jrq3-28rc](/vulnerability/GHSA-5f92-jrq3-28rc) Published Mar 10, 2026 Updated Oct 28, 2026 Affected 2 pkgs Patched 2 / 2 Exploits None indexed Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS) ## Exploitation Status ### No confirmed exploitation observed yet - CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks. - A successful exploit gives an attacker total control of the affected component, not partial access. - CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment. Exploitation and automatability from CISA’s SSVC triage for CVE-2026-30966. ## EPSS Exploitation Probability [via FIRST.org ↗](https://www.first.org/epss/) 0.4%probability of exploitation in next 30 days Lower Risk0.00% Lower risk than most CVEs34th percentile — riskier than 34% of all scored CVEsHighest risk 0.00%0.34%0.68%1.02%0.1%0.4%May 26Sep 26Nov 26 Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/). ## How urgent is this, really ## Where this sits among everything scored ## Real-World Exposure 2 pkgs affected How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched. 62other npm packages depend on this — each one inherits the vulnerability until it's patched upstream `parse-server`npm 81Kdownloads / week ## 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](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](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](https://github.com/parse-community/parse-server/releases/tag/8.6.20) ## Affected Packages 2 total 2 fixed Ecosystem Package Vulnerable range Fix 📦npm `parse-server` ≥ 9.0.0-alpha.1&&< 9.5.2-alpha.7 9.5.2-alpha.7`npm install parse-server@9.5.2-alpha.7` 📦npm `parse-server` all versions 8.6.20`npm install parse-server@8.6.20` ## Affected Products 1 product · 8 configurations Application `parse-server`parseplatform ≥ 9.0.0 && < 9.5.2 1 version 9.5.2 ## Detection & mitigation playbook Open-source dependency 1. ### Detect Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for parse-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version. 2. ### Fix Update parse-server to 9.5.2-alpha.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-30966 is resolved across your whole dependency graph. 3. ### Workarounds Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used. ## Frequently Asked Questions \### 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 O3 Security · Impact-Aware SCA ### Is CVE-2026-30966 in your dependencies? Find it across npm, including transitive dependencies. [Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)