Parse Server: Classes `_GraphQLConfig` and `_Audience` master key bypass via generic class routes
- Severity:
- High
Description
The _GraphQLConfig and _Audience internal classes can be read, modified, and deleted via the generic /classes/_GraphQLConfig and /classes/_Audience REST API routes without master key authentication. This bypasses the master key enforcement that exists on the dedicated /graphql-config and /push_audiences endpoints.
Recommendation
Update the parse-server package to the latest compatible version. Followings are version details:
Affected version(s): **< 8.6.25 >= 9.0.0-alpha.1, < 9.5.2-alpha.12** Patched version(s): **8.6.25 9.5.2-alpha.12**
References
Related Issues
- Parse Server has a protected fields bypass via LiveQuery subscription WHERE clause - CVE-2026-32098
- Parse Server has a query condition depth bypass via pre-validation transform pipeline - CVE-2026-33498
- Parse Server has a protected fields bypass via logical query operators - CVE-2026-30962
- Parse Server has a protected fields bypass via dot-notation in query and sort - CVE-2026-31872
- Tags:
- npm
- parse-server
Anything's wrong? Let us know Last updated on March 11, 2026