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.
Published Mar 12, 2026
Affected packages
parse-server
- Ecosystem
- npm
- Affected
- >= 9.0.0, < 9.6.0-alpha.9
- Fixed in
- 9.6.0-alpha.9
- Check
npm ls parse-server
parse-server
- Ecosystem
- npm
- Affected
- < 8.6.35
- Fixed in
- 8.6.35
- Check
npm ls parse-server
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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
- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-j7mm-f4rv-6q6q
- Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.9
- Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.35
Credited to offset, mtrezza.
References
- https://github.com/parse-community/parse-server/security/advisories/GHSA-j7mm-f4rv-6q6q
- https://nvd.nist.gov/vuln/detail/CVE-2026-32098
- https://github.com/parse-community/parse-server/releases/tag/8.6.35
- https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.9
- https://github.com/advisories/GHSA-j7mm-f4rv-6q6q
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-61448
Parse Server vulnerable to stored XSS via malformed Content-Type bypassing file upload extension blocklist
low2.1Oct 29, 2026CVE-2026-50008
parse-server: Server option routeAllowList is bypassable through batch sub-requests
medium6.9Jun 19, 2026CVE-2026-53724
parse-server: Stored XSS via trailing-dot filename bypassing file upload extension blocklist
low2.1Jun 19, 2026CVE-2026-53725
parse-server: Endpoints `/login` and `/verifyPassword` disclose MFA secrets and protected fields when `_User` get is denied
medium5.9Jun 19, 2026CVE-2026-53726
parse-server: Relation `$relatedTo` query bypasses `protectedFields` and owning-object ACL
medium6.9Jun 19, 2026CVE-2026-55778
parse-server: Stored XSS via non-standard file extension bypassing file upload extension blocklist
low2.1Jun 19, 2026
