Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.6.0-alpha.35 and 8.6.50, when a Parse.Cloud.afterLiveQueryEvent trigger is registered for a class, the LiveQuery server leaks protected fields and authData to all subscribers of that class. Fields configured as protected via Class-Level Permissions (protectedFields) are included in LiveQuery event payloads for all event types (create, update, delete, enter, leave). Any user with sufficient CLP permissions to subscribe to the affected class can receive protected field data of other users, including sensitive personal information and OAuth tokens from third-party authentication providers. The vulnerability was caused by a reference detachment bug. When an afterEvent trigger is registered, the LiveQuery server converts the event object to a Parse.Object for the trigger, then creates a new JSON copy via toJSONwithObjects(). The sensitive data filter was applied to the Parse.Object reference, but the unfiltered JSON copy was sent to clients. The fix in versions 9.6.0-alpha.35 and 8.6.50 ensures that the JSON copy is assigned back to the response object before filtering, so the filter operates on the actual data sent to clients. As a workaround, remove all Parse.Cloud.afterLiveQueryEvent trigger registrations. Without an afterEvent trigger, the reference detachment does not occur and protected fields are correctly filtered.
CVE-2026-33163
This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. 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
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- 34(Track)EG Risk 34/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 computedSeverity65% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 36%
- KEV
- Not listed
Published
March 18, 2026
Last Modified
June 17, 2026
Advisory Details (3)
Auto-updated Aug 6, 2026Protected fields leak via LiveQuery afterEvent trigger · Advisory · parse-community/parse-server · GitHub
https://github.com/parse-community/parse-server/security/advisories/GHSA-5hmj-jcgp-6hfffix: Protected fields leak via LiveQuery afterEvent trigger (GHSA-5hmj-jcgp-6hff)
Patch available: parse-community/parse-server 8.6.81 (PR #10233 merged 2026-03-17)
https://github.com/parse-community/parse-server/pull/10233fix: Protected fields leak via LiveQuery afterEvent trigger (GHSA-5hmj-jcgp-6hff)
Patch available: parse-community/parse-server 9.9.1-alpha.6 (PR #10232 merged 2026-03-17)
https://github.com/parse-community/parse-server/pull/10232Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| parse-server | — | 8.6.50 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 30× 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-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 18:08 UTCOSV refresh
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
Show 35 moreShow fewer
- 2026-08-24 14:17 UTCEPSS rescore
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 11:14 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 07:22 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 22:08 UTCEG score recompute
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 08:36 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 07:31 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 06:56 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 17:29 UTCEG score recompute
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 01:37 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-02 16:38 UTCEG score recompute
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-27 14:40 UTCEG score recompute
- 2026-07-27 14:27 UTCOSV refresh
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-33163?
When was CVE-2026-33163 disclosed?
Is CVE-2026-33163 actively exploited?
What is the CVSS score of CVE-2026-33163?
How do I remediate CVE-2026-33163?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33163
Is Your Infrastructure Affected by CVE-2026-33163?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.