CVE-2026-33163 Parse Server leaks protected fields via LiveQuery afterEvent trigger
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: yes · technical impact: partial
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.
Upgrade path
3 packages: 2 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| npm parse-server(npm) | < 8.6.50; >= 9.0.0, < 9.6.0-alpha.35 | 8.6.50, 9.6.0-alpha.35 | Fixed |
| parseplatform parse-server | < 8.6.50; = 9.6.0-alpha1; = 9.6.0-alpha2; = 9.6.0-alpha3 +32 more | 8.6.50, 9.6.0 | Fixed |
| parse-community parse-server | = < 8.6.50; = >= 9.0.0, < 9.6.0-alpha.35 | No fix listed | Versions listed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| parse-community parse-server | = >= 9.0.0, < 9.6.0-alpha.35 | No fix listed |
| parse-community parse-server | = < 8.6.50 | No fix listed |
| npm parse-server(npm) | >= 9.0.0, < 9.6.0-alpha.35 | 9.6.0-alpha.35 |
| npm parse-server(npm) | < 8.6.50 | 8.6.50 |
| parseplatform parse-server | < 8.6.50 | 8.6.50 |
| parseplatform parse-server | >= 9.0.0, < 9.6.0 | 9.6.0 |
| parseplatform parse-server | = 9.6.0-alpha1 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha10 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha11 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha12 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha13 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha14 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha15 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha16 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha17 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha18 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha19 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha2 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha20 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha21 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha22 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha23 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha24 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha25 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha26 | No fix listed |
Show 15 more
| Product | Affected versions | Fixed in |
|---|---|---|
| parseplatform parse-server | = 9.6.0-alpha27 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha28 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha29 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha3 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha30 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha31 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha32 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha33 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha34 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha4 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha5 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha6 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha7 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha8 | No fix listed |
| parseplatform parse-server | = 9.6.0-alpha9 | No fix listed |
References
- https://github.com/parse-community/parse-server/security/advisories/GHSA-5hmj-jcgp-6hff vendor-advisory
- https://github.com/parse-community/parse-server/pull/10232 issue-tracking patch
- https://github.com/parse-community/parse-server/pull/10233 issue-tracking patch
- nvd.nist.gov third-party-advisory vendor-advisory
- github.com
- github.com product