parse-community parse-server up to 8.6.33/9.0.0 9.6.0-alpha.7 Email Verification Endpoint response discrepancy

Summaryinfo

A vulnerability was found in parse-community parse-server up to 8.6.33/9.0.0 9.6.0-alpha.7. It has been classified as problematic. This vulnerability affects unknown code of the component Email Verification Endpoint. This manipulation causes response discrepancy. This vulnerability is handled as CVE-2026-31901. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as problematic was found in parse-community parse-server up to 8.6.33/9.0.0 9.6.0-alpha.7. Affected by this vulnerability is an unknown code block of the component Email Verification Endpoint. The manipulation with an unknown input leads to a response discrepancy vulnerability. The CWE definition for the vulnerability is CWE-204. The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere. As an impact it is known to affect confidentiality. 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 8.6.34 and 9.6.0-alpha.8, the email verification endpoint (/verificationEmailRequest) returns distinct error responses depending on whether an email address belongs to an existing user, is already verified, or does not exist. An attacker can send requests with different email addresses and observe the error codes to determine which email addresses are registered in the application. This is a user enumeration vulnerability that affects any Parse Server deployment with email verification enabled (verifyUserEmails: true). This vulnerability is fixed in 8.6.34 and 9.6.0-alpha.8.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-31901 since 03/09/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

Upgrading to version 8.6.34 or 9.0.0 9.6.0-alpha.8 eliminates this vulnerability.

Be aware that VulDB is the high quality source for vulnerability data.

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
• 8.6.25
• 8.6.26
• 8.6.27
• 8.6.28
• 8.6.29
• 8.6.30
• 8.6.31
• 8.6.32
• 8.6.33
• 9.0.0 9.6.0-alpha.0
• 9.0.0 9.6.0-alpha.1
• 9.0.0 9.6.0-alpha.2
• 9.0.0 9.6.0-alpha.3
• 9.0.0 9.6.0-alpha.4
• 9.0.0 9.6.0-alpha.5
• 9.0.0 9.6.0-alpha.6
• 9.0.0 9.6.0-alpha.7

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

Be aware that VulDB is the high quality source for vulnerability data.

Discussion