CVE-2026-33429: Parse Server has a protected field change detection oracle via LiveQuery watch parameter
Impact An attacker can subscribe to LiveQuery with a watch parameter targeting a protected field. Although the protected field value is properly stripped from event payloads, the presence or absence of update events reveals whether the protected field changed, creating a binary oracle. For boolean protected fields, the timing of change events is equivalent to knowing the field value.
Published Mar 20, 2026 · Updated Mar 30, 2026
Affected packages
parse-server
- Ecosystem
- npm
- Affected
- >= 9.0.0, < 9.6.0-alpha.43
- Fixed in
- 9.6.0-alpha.43
- Check
npm ls parse-server
parse-server
- Ecosystem
- npm
- Affected
- < 8.6.54
- Fixed in
- 8.6.54
- Check
npm ls parse-server
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
An attacker can subscribe to LiveQuery with a watch parameter targeting a protected field. Although the protected field value is properly stripped from event payloads, the presence or absence of update events reveals whether the protected field changed, creating a binary oracle. For boolean protected fields, the timing of change events is equivalent to knowing the field value.
Patches
The watch parameter is now validated against protected fields at subscription time, mirroring the existing validation for the where clause. Subscriptions that include protected fields in watch are rejected with a permission error. Master key connections are exempt.
Workarounds
None.
Credited to offset, mtrezza.
References
- https://github.com/parse-community/parse-server/security/advisories/GHSA-qpc3-fg4j-8hgm
- https://github.com/parse-community/parse-server/pull/10253
- https://github.com/parse-community/parse-server/pull/10254
- https://nvd.nist.gov/vuln/detail/CVE-2026-33429
- https://github.com/parse-community/parse-server/commit/0c0a0a5a37ca821d2553119f2cb3be35322eda4b
- https://github.com/parse-community/parse-server/commit/c62eacaf38de86913f09240583448360b1cc8e67
- https://github.com/advisories/GHSA-qpc3-fg4j-8hgm
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
