Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.54 and 9.6.0-alpha.43, an attacker can subscribe to LiveQuery with a watch parameter targeting a protected field. Although the protected field value is properly stripped from event payloads, the presence or absence of update events reveals whether the protected field changed, creating a binary oracle. For boolean protected fields, the timing of change events is equivalent to knowing the field value. This issue has been patched in versions 8.6.54 and 9.6.0-alpha.43.
CVE-2026-33429
This medium-severity CVE scores 5.3 under NVD CVSS v3. 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(low)
- EG Risk
- 28(Track)EG Risk 28/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 computedSeverity53% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
March 24, 2026
Last Modified
June 17, 2026
References (5)
- security-advisories@githubhttps://github.com/parse-community/parse-server/commit/0c0a0a5a37ca821d2553119f2cb3be35322eda4b
- security-advisories@githubhttps://github.com/parse-community/parse-server/commit/c62eacaf38de86913f09240583448360b1cc8e67
- security-advisories@githubhttps://github.com/parse-community/parse-server/pull/10253
- security-advisories@githubhttps://github.com/parse-community/parse-server/pull/10254
- security-advisories@githubhttps://github.com/parse-community/parse-server/security/advisories/GHSA-qpc3-fg4j-8hgm
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× 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.
- 2026-07-27 14:29 UTCEG score recompute
- 2026-07-27 14:27 UTCOSV refresh
Related CVEs(same CWE)
Same CWE
10 shownCWE-203
- CVE-2019-10071EG 9.8EPSS p95CRITICAL
- CVE-2018-1000884EG 9.8CRITICAL
- CVE-2017-5753NVD 5.6EG 9.0EPSS p100CRITICAL
- CVE-2017-5715NVD 5.6EG 8.3EPSS p99HIGH
- CVE-2019-10233EG 8.1HIGH
- CVE-2018-9364EG 7.5HIGH
- CVE-2013-10006NVD 2.6EG 7.5HIGH
- CVE-2019-1020002EG 7.5HIGH
- CVE-2019-10114EG 7.5HIGH
- CVE-2017-13099NVD 5.9EG 7.5EPSS p98HIGH
Frequently asked(4)
What is CVE-2026-33429?
When was CVE-2026-33429 disclosed?
What is the CVSS score of CVE-2026-33429?
How do I remediate CVE-2026-33429?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-33429
Is Your Infrastructure Affected by CVE-2026-33429?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.