CVE-2026-31800: Parse Server: Classes `_GraphQLConfig` and `_Audience` master key bypass via generic class routes

Published Mar 10, 2026
·
Updated

Impact

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 /pushaudiences endpoints. An attacker can read, modify and delete GraphQL configuration and push audience data.

Patches

The fix adds the affected internal classes to the classesWithMasterOnlyAccess list, ensuring that the generic /classes/ routes enforce master key access consistently with the dedicated endpoints.

Workarounds

There is no known workaround.

References

- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-7xg7-rqf6-pw6c - Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.2-alpha.12 - Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.25

Other sources

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.5.2-alpha.12 and 8.6.25, 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 /pushaudiences endpoints. An attacker can read, modify and delete GraphQL configuration and push audience data. This vulnerability is fixed in 9.5.2-alpha.12 and 8.6.25.

MITRE

Affected Software

16 affected componentsFixes available
npm/parse-server<9.5.2-alpha.12, <8.6.25
npm/parse-server<8.6.25
8.6.25
npm/parse-server>=9.0.0-alpha.1<9.5.2-alpha.12
9.5.2-alpha.12
parseplatform Parse-server Node.js<8.6.25
parseplatform Parse-server Node.js>=9.0.0<9.5.2
parseplatform Parse-server Node.js=9.5.2-alpha1
parseplatform Parse-server Node.js=9.5.2-alpha10
parseplatform Parse-server Node.js=9.5.2-alpha11
parseplatform Parse-server Node.js=9.5.2-alpha2
parseplatform Parse-server Node.js=9.5.2-alpha3
parseplatform Parse-server Node.js=9.5.2-alpha4
parseplatform Parse-server Node.js=9.5.2-alpha5
parseplatform Parse-server Node.js=9.5.2-alpha6
parseplatform Parse-server Node.js=9.5.2-alpha7
parseplatform Parse-server Node.js=9.5.2-alpha8
parseplatform Parse-server Node.js=9.5.2-alpha9

Event History

Mar 10, 2026
CVE Published
via MITRE·08:51 PM
Data Sourced
via MITRE·08:51 PM
DescriptionWeakness
Data Sourced
via NVD·09:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Mar 11, 2026
Advisory Published
via GitHub·12:23 AM
Data Sourced
via GitHub·12:23 AM
DescriptionWeaknessAffected Software
Jul 22, 58183
Event
via NVD·03:42 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-31800?

CVE-2026-31800 is considered a critical vulnerability due to its potential to allow unauthorized modifications to sensitive internal classes.

2

How do I fix CVE-2026-31800?

To fix CVE-2026-31800, upgrade your Parse Server to version 8.6.25 or 9.5.2-alpha.12 or later.

3

What systems are affected by CVE-2026-31800?

CVE-2026-31800 affects Parse Server versions up to 8.6.25 and versions between 9.0.0-alpha.1 to 9.5.2-alpha.12.

4

What components of Parse Server are vulnerable in CVE-2026-31800?

The vulnerable components in CVE-2026-31800 are the internal classes `_GraphQLConfig` and `_Audience' accessed via generic REST API routes.

5

Can CVE-2026-31800 lead to data loss or corruption?

Yes, CVE-2026-31800 can lead to data loss or corruption as it allows unauthorized users to modify or delete sensitive internal class data.

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