parse-community parse-server up to 8.6.24/9.0.0 9.5.2-alpha.11 authorization

Summaryinfo

A vulnerability classified as critical has been found in parse-community parse-server up to 8.6.24/9.0.0 9.5.2-alpha.11. This affects an unknown function. The manipulation leads to authorization. This vulnerability is uniquely identified as CVE-2026-31800. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in parse-community parse-server up to 8.6.24/9.0.0 9.5.2-alpha.11. This issue affects some unknown processing. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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 /push_audiences 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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-31800 since 03/09/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.

Upgrading to version 8.6.25 or 9.0.0 9.5.2-alpha.12 eliminates this vulnerability. The upgrade is hosted for download at github.com.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• parse-community

Name

• parse-server

Version

• 8.6.0
• 8.6.1
• 8.6.2
• 8.6.3
• 8.6.4
• 8.6.5
• 8.6.6
• 8.6.7
• 8.6.8
• 8.6.9
• 8.6.10
• 8.6.11
• 8.6.12
• 8.6.13
• 8.6.14
• 8.6.15
• 8.6.16
• 8.6.17
• 8.6.18
• 8.6.19
• 8.6.20
• 8.6.21
• 8.6.22
• 8.6.23
• 8.6.24
• 9.0.0 9.5.2-alpha.0
• 9.0.0 9.5.2-alpha.1
• 9.0.0 9.5.2-alpha.2
• 9.0.0 9.5.2-alpha.3
• 9.0.0 9.5.2-alpha.4
• 9.0.0 9.5.2-alpha.5
• 9.0.0 9.5.2-alpha.6
• 9.0.0 9.5.2-alpha.7
• 9.0.0 9.5.2-alpha.8
• 9.0.0 9.5.2-alpha.9
• 9.0.0 9.5.2-alpha.10
• 9.0.0 9.5.2-alpha.11

Website

• Product: https://github.com/parse-community/parse-server/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion