~ / search / GHSA-r2m8-pxm9-9c4g

GHSA-r2m8-pxm9-9c4g

Parse Server has a protected fields bypass via dot-notation in query and sort

Source: GitHub Advisory Database (reviewed) High CVE-2026-31872

Packages

EcosystemPackageAffectedFixed in
npm parse-server >= 9.0.0-alpha.1, < 9.6.0-alpha.6 9.6.0-alpha.6
npm parse-server < 8.6.32 8.6.32

Details

As written in the advisory (Markdown source, shown as plain text).

### Impact The `protectedFields` class-level permission (CLP) can be bypassed using dot-notation in query WHERE clauses and sort parameters. An attacker can use dot-notation to query or sort by sub-fields of a protected field, enabling a binary oracle attack to enumerate protected field values. This affects both MongoDB and PostgreSQL deployments. ### Patches The fix ensures that query WHERE clause keys and sort keys are checked against protected fields by extracting the root field from dot-notation paths. For example, a query on `secretObj.apiKey` is now correctly blocked when `secretObj` is a protected field. ### Workarounds None. ### References - GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-r2m8-pxm9-9c4g - Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.6 - Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.32

References

External links from the advisory. They lead to third-party sites.