cve.bz

CVE-2026-33163 parseplatform parse-server

8.2 highEPSS 0.5%Fix available

High (8.2) in parseplatform parse-server. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in parse-server 8.6.50, 9.6.0-alpha.35.

On this page
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.

Severity

CVSS 4.0

8.2 high
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 42nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-03-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-33163 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-33163?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-33163?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-33163 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
parseplatform:parse-serverbefore 8.6.50
parseplatform:parse-serverfrom 9.0.0 before 9.6.0
parseplatform:parse-server9.6.0:alpha1
parseplatform:parse-server9.6.0:alpha10
parseplatform:parse-server9.6.0:alpha11
parseplatform:parse-server9.6.0:alpha12
parseplatform:parse-server9.6.0:alpha13
parseplatform:parse-server9.6.0:alpha14
parseplatform:parse-server9.6.0:alpha15
parseplatform:parse-server9.6.0:alpha16
parseplatform:parse-server9.6.0:alpha17
parseplatform:parse-server9.6.0:alpha18
parseplatform:parse-server9.6.0:alpha19
parseplatform:parse-server9.6.0:alpha2
parseplatform:parse-server9.6.0:alpha20
parseplatform:parse-server9.6.0:alpha21
parseplatform:parse-server9.6.0:alpha22
parseplatform:parse-server9.6.0:alpha23
parseplatform:parse-server9.6.0:alpha24
parseplatform:parse-server9.6.0:alpha25
parseplatform:parse-server9.6.0:alpha26
parseplatform:parse-server9.6.0:alpha27
parseplatform:parse-server9.6.0:alpha28
parseplatform:parse-server9.6.0:alpha29
parseplatform:parse-server9.6.0:alpha3
parseplatform:parse-server9.6.0:alpha30
parseplatform:parse-server9.6.0:alpha31
parseplatform:parse-server9.6.0:alpha32
parseplatform:parse-server9.6.0:alpha33
parseplatform:parse-server9.6.0:alpha34
parseplatform:parse-server9.6.0:alpha4
parseplatform:parse-server9.6.0:alpha5
parseplatform:parse-server9.6.0:alpha6
parseplatform:parse-server9.6.0:alpha7
parseplatform:parse-server9.6.0:alpha8
parseplatform:parse-server9.6.0:alpha9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-5hmj-jcgp-6hffnpmparse-server>=9.0.0 <9.6.0-alpha.359.6.0-alpha.35
GHSA-5hmj-jcgp-6hffnpmparse-server<8.6.508.6.50

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON