CVE-2026-30962

Description

### Impact The validation for protected fields only checks top-level query keys. By wrapping a query constraint on a protected field inside a logical operator, the check is bypassed entirely. This allows any authenticated user to query on protected fields to extract field values. All Parse Server deployments have default protected fields and are vulnerable. ### Patches The fix adds recursive validation of sub-queries with logical operators, consistent with the existing recursive validation patterns. ### Workarounds Use a `beforeFind` trigger on affected classes to manually inspect the query for protected field references in logical operator sub-queries and reject the request. ### References - GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-72hp-qff8-4pvv - Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.2-alpha.6 - Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.19

How to fix CVE-2026-30962

To remediate CVE-2026-30962, upgrade the affected package to a fixed version below.

• —upgrade to 8.6.19 or later
• —upgrade to 9.5.2-alpha.6 or later

Is CVE-2026-30962 being exploited?

Low — EPSS is 0.0%, meaning exploitation activity has not been observed at scale.

Affected packages (2)

• from 0, < 8.6.19, >= 9.0.0, < 9.5.2
• >= 9.0.0, < 9.5.2-alpha.6

CVSS scores

References (5)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2026-30962
• PATCHgithub.com/parse-community/parse-server
• WEBgithub.com/parse-community/parse-server/releases/tag/8.6.19
• WEBgithub.com/parse-community/parse-server/releases/tag/9.5.2-alpha.6