CVE-2026-31872: Parse Server has a protected fields bypass via dot-notation in query and sort

Published Mar 11, 2026
·
Updated

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

Other sources

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.6.0-alpha.6 and 8.6.32, 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. This vulnerability is fixed in 9.6.0-alpha.6 and 8.6.32.

MITRE

Affected Software

9 affected componentsFixes available
npm/parse-server<8.6.32
8.6.32
npm/parse-server>=9.0.0-alpha.1<9.6.0-alpha.6
9.6.0-alpha.6
parseplatform Parse-server Node.js<8.6.32
parseplatform Parse-server Node.js>=9.0.0<9.6.0
parseplatform Parse-server Node.js=9.6.0-alpha1
parseplatform Parse-server Node.js=9.6.0-alpha2
parseplatform Parse-server Node.js=9.6.0-alpha3
parseplatform Parse-server Node.js=9.6.0-alpha4
parseplatform Parse-server Node.js=9.6.0-alpha5

Event History

Mar 11, 2026
Advisory Published
via GitHub·12:34 AM
Data Sourced
via GitHub·12:34 AM
DescriptionWeaknessAffected Software
CVE Published
via MITRE·06:02 PM
Data Sourced
via MITRE·06:02 PM
DescriptionWeakness
Data Sourced
via NVD·06:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jan 29, 58178
Event
via FIRST·08:29 PM

Frequently Asked Questions

1

What is the severity of CVE-2026-31872?

CVE-2026-31872 has a high severity rating due to its potential for bypassing class-level permissions and enabling unauthorized data access.

2

How do I fix CVE-2026-31872?

To mitigate CVE-2026-31872, upgrade to Parse Server version 8.6.32 or 9.6.0-alpha.6 or later, ensuring the vulnerability is patched.

3

What software is affected by CVE-2026-31872?

CVE-2026-31872 affects Parse Server versions prior to 8.6.32 and between 9.0.0-alpha.1 and 9.6.0-alpha.6.

4

What type of attack is enabled by CVE-2026-31872?

CVE-2026-31872 allows for a binary oracle attack through the use of dot-notation in queries on protected fields.

5

What is the impact of CVE-2026-31872?

The impact of CVE-2026-31872 includes unauthorized access to sensitive data and the enumeration of protected field values.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203