All reports
Medium

Parse Server has a protected fields bypass via LiveQuery subscription WHERE clause

Affected versions

Affected versions
< 8.6.35
Fixed version
8.6.35
Affected versions
>= 9.0.0, < 9.6.0-alpha.9
Fixed version
9.6.0-alpha.9

Exploitation

CVE-2026-32098

Probability of exploitation in the next 30 days: 0.33%

FIRST EPSS · 2026-11-21

Description

Impact

An attacker can exploit LiveQuery subscriptions to infer the values of protected fields without directly receiving them. By subscribing with a WHERE clause that references a protected field (including via dot-notation or $regex), the attacker can observe whether LiveQuery events are delivered for matching objects. This creates a boolean oracle that leaks protected field values. The attack affects any class that has both protectedFields configured in Class-Level Permissions and LiveQuery enabled.

Patches

The fix adds validation of the LiveQuery subscription WHERE clause against the class's protected fields, mirroring the existing REST API validation. If a subscription's WHERE clause references a protected field directly, via dot-notation, or inside $or / $and / $nor operators, the subscription is rejected with a permission error. This is applied during subscription creation, so existing event delivery paths are not affected.

Workarounds

Disable LiveQuery for classes that use protectedFields in their Class-Level Permissions, or remove protectedFields from classes that require LiveQuery.

References

Links

Credits

  • offset
  • mtrezza