parse-server
Affected
- introduced
9.0.0, fixed9.6.0-alpha.9(semver)
Fixed versions
9.6.0-alpha.9
Fix
- Fixed version
9.6.0-alpha.9npm install [email protected]
Advisory
Also known as: BIT-parse-2026-32098, CVE-2026-32098
Parse Server has a protected fields bypass via LiveQuery subscription WHERE clause
Impact
An attacker can exploit LiveQuery subscriptions to infer the values of protected fields without directly receiving them. By subscribing with a WHERE clause that references a protected field (including via dot-notation or $regex), the attacker can observe whether LiveQuery events are delivered for matching objects. This creates a boolean oracle that leaks protected field values. The attack affects any class that has both protectedFields configured in Class-Level Permissions and LiveQuery enabled.
Patches
The fix adds validation of the LiveQuery subscription WHERE clause against the class's protected fields, mirroring the existing REST API validation. If a subscription's WHERE clause references a protected field directly, via dot-notation, or inside $or / $and / $nor operators, the subscription is rejected with a permission error. This is applied during subscription creation, so existing event delivery paths are not affected.
Workarounds
Disable LiveQuery for classes that use protectedFields in their Class-Level Permissions, or remove protectedFields from classes that require LiveQuery.
References
Medium Basis: The source's own band: MODERATE
9.0.0, fixed 9.6.0-alpha.9 (semver)9.6.0-alpha.9
9.6.0-alpha.9npm install [email protected]0, fixed 8.6.35 (semver)8.6.35
8.6.35npm 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