CVE-2026-31800

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

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

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

Kodem intelligence

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.

1. What is CVE-2026-31800? CVE-2026-31800 is a high-severity missing authorization vulnerability in parse-server (npm), affecting versions >= 9.0.0-alpha.1, < 9.5.2-alpha.12. It is fixed in 9.5.2-alpha.12, 8.6.25. The application does not perform an authorization check before performing a sensitive operation.
2. Which versions of parse-server are affected by CVE-2026-31800? parse-server (npm) versions >= 9.0.0-alpha.1, < 9.5.2-alpha.12 is affected.
3. Is there a fix for CVE-2026-31800? Yes. CVE-2026-31800 is fixed in 9.5.2-alpha.12, 8.6.25. Upgrade to this version or later.
4. Is CVE-2026-31800 exploitable, and should I be worried? Whether CVE-2026-31800 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2026-31800 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2026-31800?
   • Upgrade parse-server to 9.5.2-alpha.12 or later
   • Upgrade parse-server to 8.6.25 or later

Other vulnerabilities in parse-server