Advisory

GHSA-j7mm-f4rv-6q6q

Also known as: BIT-parse-2026-32098, CVE-2026-32098

Summary

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

Details

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

  • GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-j7mm-f4rv-6q6q
  • Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.9
  • Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.35

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-03-12 14:20 UTC
Modified
2026-03-14 02:41 UTC

Affected packages and fixes

parse-server

npm · All systems

Affected

  • introduced 9.0.0, fixed 9.6.0-alpha.9 (semver)

Fixed versions

9.6.0-alpha.9

Fix

parse-server

npm · All systems

Affected

  • introduced 0, fixed 8.6.35 (semver)

Fixed versions

8.6.35

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences