NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-33429: Parse Server has a protected field change detection oracle via LiveQuery watch parameter

mediumCVSS 4.0 6.3 · 3.1 5.3GHSA-qpc3-fg4j-8hgm

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

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 entries