CVE-2026-100632
Last modified
CVE-2026-100632 is a medium-severity vulnerability rated 6.5/10 on the CVSS scale. 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.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| parse-community | parse-server | >= 9.0.0, < 9.10.1-alpha.8 |
| parse-community | parse-server | < 8.6.89 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-100632?
How severe is CVE-2026-100632?
How do I fix CVE-2026-100632?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-100627Capgo (Cap-go/capgo.app) server backend Supabase functions c…8.1
- CVE-2026-100628capgo.app before 12.128.12 fails to enforce an organization'…4.3
- CVE-2026-100629Capgo (capgo.app backend) before 12.127.5 contains an author…5.5
- CVE-2026-10063A vulnerability was identified in TRENDnet TEW-432BRP 3.10B2…9.8
- CVE-2026-100630AVideo contains a stored cross-site scripting vulnerability …5.4
- CVE-2026-100631Parse Server is an open source backend server. In versions p…7.5
- CVE-2026-100633SiYuan is a self-hosted personal knowledge management system…6.5
- CVE-2026-100634SiYuan before v3.8.4 does not validate the sender or restric…4.7
- CVE-2026-100635SiYuan before v3.8.4 contains an authentication bypass vulne…5.9
- CVE-2026-100636SiYuan versions before v3.8.4 contain a path traversal vulne…7.6
- CVE-2026-100637SiYuan versions before v3.8.4 contain a path traversal vulne…7.6
- CVE-2026-100638SiYuan versions before v3.8.4 contain a path traversal vulne…7.6
Are you affected by CVE-2026-100632?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
