CVE-2026-30966

CRITICALPre-NVD 10.010.0
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 10.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 10.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
10.0
EG Score
10.0(low)
EG Risk
50(Track)
EG Risk 50/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity100% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

March 10, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Jul 27, 2026
Patch available. Sources: github_release, github.
github Patch Available

Parse Server role escalation and CLP bypass via direct `_Join` table write · Advisory · parse-community/parse-server · GitHub

https://github.com/parse-community/parse-server/security/advisories/GHSA-5f92-jrq3-28rc
github_release Patch Available

9.5.2-alpha.7

Patch available: parse-community/parse-server 9.5.2-alpha.7 (pre-release)

https://github.com/parse-community/parse-server/releases/tag/9.5.2-alpha.7
github_release Patch Available

8.6.20

Patch available: parse-community/parse-server 8.6.20

https://github.com/parse-community/parse-server/releases/tag/8.6.20

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
parse-server—9.5.2-alpha.7—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 4× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-30 16:27 UTCEPSS rescore
  2. 2026-07-30 01:30 UTCEPSS rescore
  3. 2026-07-28 15:36 UTCEPSS rescore
  4. 2026-07-27 13:44 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-30966?
CVE-2026-30966 is a critical vulnerability published on March 10, 2026. 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…
When was CVE-2026-30966 disclosed?
CVE-2026-30966 was first published in the National Vulnerability Database on March 10, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-30966 actively exploited?
CVE-2026-30966 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 68.9% of all scored CVEs.
What is the CVSS score of CVE-2026-30966?
CVE-2026-30966 has a CVSS v3 base score of 10.0 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-30966?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-30966, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-30966

Explore →

Is Your Infrastructure Affected by CVE-2026-30966?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs