CVE-2026-31800

Description

### 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 `/push_audiences` 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

How to fix CVE-2026-31800

To remediate CVE-2026-31800, upgrade the affected package to a fixed version below.

• —upgrade to 8.6.25 or later
• —upgrade to 9.5.2-alpha.12 or later

Is CVE-2026-31800 being exploited?

Low — EPSS is 0.1%, meaning exploitation activity has not been observed at scale.

Affected packages (2)

• from 0, < 8.6.25, >= 9.0.0, < 9.5.2
• >= 9.0.0-alpha.1, < 9.5.2-alpha.12

CVSS scores

References (5)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2026-31800
• PATCHgithub.com/parse-community/parse-server
• WEBgithub.com/parse-community/parse-server/releases/tag/8.6.25
• WEBgithub.com/parse-community/parse-server/releases/tag/9.5.2-alpha.12