parse-server
Affected
- introduced
9.0.0, fixed9.7.0-alpha.9(semver)
Fixed versions
9.7.0-alpha.9
Fix
- Fixed version
9.7.0-alpha.9npm install [email protected]
Advisory
Also known as: BIT-parse-2026-34363, CVE-2026-34363
LiveQuery protected field leak via shared mutable state across concurrent subscribers
Impact
When multiple clients subscribe to the same class via LiveQuery, the event handlers process each subscriber concurrently using shared mutable objects. The sensitive data filter modifies these shared objects in-place, so when one subscriber's filter removes a protected field, subsequent subscribers may receive the already-filtered object. This can cause protected fields and authentication data to leak to clients that should not see them, or cause clients that should see the data to receive an incomplete object.
Additionally, when an afterEvent Cloud Code trigger is registered, one subscriber's trigger modifications can leak to other subscribers through the same shared mutable state.
Any Parse Server deployment using LiveQuery with protected fields or afterEvent triggers is affected when multiple clients subscribe to the same class.
Patches
The fix deep-clones the shared objects at the start of each subscriber's processing callback, ensuring each subscriber works on an independent copy. Additionally, a bug was fixed where master key LiveQuery clients could not receive events on classes with protected fields due to an incorrect type passed to the sensitive data filter.
Workarounds
There is no known workaround.
Resources
High Basis: The source's own band: HIGH
9.0.0, fixed 9.7.0-alpha.9 (semver)9.7.0-alpha.9
9.7.0-alpha.9npm install [email protected]0, fixed 8.6.65 (semver)8.6.65
8.6.65npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0