Parse Server 9.0.0 before 9.10.1 Protected Fields Disclosure via LiveQuery

Summary

Parse Server is an open-source backend server. In versions >= 9.0.0 and < 9.10.1-alpha.8, and in versions < 8.6.89, LiveQuery evaluates the protectedFields class-level permission against an incompletely resolved caller identity: the subscriber's roles are not resolved, and when a subscription does not supply its own session token the event payload is redacted against an anonymous identity even though the read was authorized against the connected user. As a result, field masks defined for a role, for authenticated users, or for a specific user are not applied, so an authenticated subscriber can receive field values that the REST API correctly withholds and can use a masked field to filter or watch a subscription. Only classes with LiveQuery enabled that define protectedFields under a role:, authenticated, or per-user group are affected; masks under the public () group are applied correctly. The issue is fixed in 9.10.1-alpha.8 and 8.6.89. As a workaround, additionally define the affected field masks under the public () group, or disable LiveQuery for classes whose class-level permissions rely on role-scoped, authenticated, or per-user protectedFields groups.

Timeline

1. Sep 26, 2026, 1:23 PM UTCCVE published
2. Sep 28, 2026, 4:48 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Sep 28, 2026, 4:49 PM UTCRecord last updated

Affected versions

• parse-community parse-server

  From 9.0.0 · fixed in 9.10.1-alpha.8

• parse-community parse-server

  fixed in 8.6.89

• parseBitnami

  fixed in 8.6.89; From 9.0.0 · fixed in 9.10.1

References 2