GHSA-qpc3-fg4j-8hgm
Parse Server has a protected field change detection oracle via LiveQuery watch parameter
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| npm | parse-server | >= 9.0.0, < 9.6.0-alpha.43 | 9.6.0-alpha.43 |
| npm | parse-server | < 8.6.54 | 8.6.54 |
Details
As written in the advisory (Markdown source, shown as plain text).
### 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.
References
External links from the advisory. They lead to third-party sites.
- https://github.com/parse-community/parse-server/security/advisories/GHSA-qpc3-fg4j-8hgm
- https://nvd.nist.gov/vuln/detail/CVE-2026-33429
- https://github.com/parse-community/parse-server/pull/10253
- https://github.com/parse-community/parse-server/pull/10254
- https://github.com/parse-community/parse-server/commit/0c0a0a5a37ca821d2553119f2cb3be35322eda4b
- https://github.com/parse-community/parse-server/commit/c62eacaf38de86913f09240583448360b1cc8e67
- https://github.com/parse-community/parse-server