GitHub Advisoryadvisory · npm
GHSA-qpc3-fg4j-8hgm Parse Server has a protected field change detection oracle via LiveQuery watch parameter
MEDIUM
Official page ↗
- Aliases
- CVE-2026-33429
- Ecosystem
- npm
- Packages
- parse-server
- Severity
- Moderate
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- Weaknesses
- CWE-203
- Reviewed
- 2026-03-20
Affected packages
• npm parse-server: >= 9.0.0, < 9.6.0-alpha.43 → fixed in 9.6.0-alpha.43
• npm parse-server: < 8.6.54 → fixed in 8.6.54
Description
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.
Related
Alias · CVE (1)
- CVE-2026-33429 Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. vulnerability
Weakness · CWE (1)
- CWE-203 Observable Discrepancy weakness
References
- https://github.com/parse-community/parse-server/security/advisories/GHSA-qpc3-fg4j-8hgm web
- https://nvd.nist.gov/vuln/detail/CVE-2026-33429 advisory
- https://github.com/parse-community/parse-server/pull/10253 web
- https://github.com/parse-community/parse-server/pull/10254 web
- https://github.com/parse-community/parse-server/commit/0c0a0a5a37ca821d2553119f2cb3be35322eda4b web
- https://github.com/parse-community/parse-server/commit/c62eacaf38de86913f09240583448360b1cc8e67 web
- https://github.com/parse-community/parse-server package