Quick answers
- Is CVE-2026-100632 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100632 being exploited in the wild.
- How severe is CVE-2026-100632?
- Medium severity, with a CVSS score of 6.5, published 26 September 2026.
- Which products and versions are affected?
- Parse Community Parse Server versions >= 9.0.0 and < 9.10.1-alpha.8, and versions < 8.6.89.
- Is there a fix for CVE-2026-100632?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-100632 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-100632?
- Check whether you run Parse Community Parse Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
LiveQuery evaluates protectedFields permissions against an incompletely resolved subscriber identity, failing to apply field masks defined for roles, authenticated users, or specific users. When a subscription lacks its own session token, the event payload is redacted against an anonymous identity even though the read was authorized against the connected user. An authenticated subscriber can exploit this to receive masked field values and use them to filter or watch subscriptions, bypassing intended access controls on role-scoped, authenticated, or per-user field groups.
Affected products
- Parse Community Parse Server versions >= 9.0.0 and < 9.10.1-alpha.8, and versions < 8.6.89
Timeline
- 2026-09-26: disclosed: Published by Parse Community