← Back

CVE-2026-33163

nvd nist
Published: Mar 18, 2026Modified: Jun 17, 2026

JSON object

Loading...
8.2
Vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Show more
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XShow less
Source: security-advisories@github.com (Secondary)

Description

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.

Affected (36)

1 product
Parse Server
Configuration A
36 vulnerable
Vulnerable SoftwareAffected Versions
Parseplatform
Before 8.6.50
From 9.0.0 to 9.6.0
Version 9.6.0 alpha10
Version 9.6.0 alpha11
Version 9.6.0 alpha12
Version 9.6.0 alpha13
Version 9.6.0 alpha14
Version 9.6.0 alpha15
Version 9.6.0 alpha16
Version 9.6.0 alpha17
Version 9.6.0 alpha18
Version 9.6.0 alpha19
Version 9.6.0 alpha1
Version 9.6.0 alpha20
Version 9.6.0 alpha21
Version 9.6.0 alpha22
Version 9.6.0 alpha23
Version 9.6.0 alpha24
Version 9.6.0 alpha25
Version 9.6.0 alpha26
Version 9.6.0 alpha27
Version 9.6.0 alpha28
Version 9.6.0 alpha29
Version 9.6.0 alpha2
Version 9.6.0 alpha30
Version 9.6.0 alpha31
Version 9.6.0 alpha32
Version 9.6.0 alpha33
Version 9.6.0 alpha34
Version 9.6.0 alpha3
Version 9.6.0 alpha4
Version 9.6.0 alpha5
Version 9.6.0 alpha6
Version 9.6.0 alpha7
Version 9.6.0 alpha8
Version 9.6.0 alpha9

References (3)

Source: security-advisories@github.com
Issue Tracking
Source: security-advisories@github.com
Issue Tracking

Timeline

No history available yet.