CVE-2026-33323 | parse-community parse-server up to 8.6.50/9.6.0-alpha.39 Configuration Options response discrepancy (GHSA-h29g-q5c2-9h4f)

VDB-352846 · CVE-2026-33323 · GHSA-H29G-Q5C2-9H4F PARSE-COMMUNITY PARSE-SERVER UP TO 8.6.50/9.6.0-ALPHA.39 CONFIGURATION OPTIONS RESPONSE DISCREPANCY HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.1 $0-$5k 0.58+ Summaryinfo A vulnerability was found in parse-community parse-server up to 8.6.50/9.6.0-alpha.39 and classified as problematic. Affected is an unknown function of the component Configuration Options Handler. Executing a manipulation can lead to response discrepancy. This vulnerability is handled as CVE-2026-33323. The attack can be executed remotely. There is not any exploit available. It is suggested to upgrade the affected component. Detailsinfo A vulnerability classified as problematic was found in parse-community parse-server up to 8.6.50/9.6.0-alpha.39. This vulnerability affects an unknown code of the component Configuration Options Handler. 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. CVE summarizes: Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.51 and 9.6.0-alpha.40, the Pages route and legacy PublicAPI route for resending email verification links return distinguishable responses depending on whether the provided username exists and has an unverified email. This allows an unauthenticated attacker to enumerate valid usernames by observing different redirect targets. The existing emailVerifySuccessOnInvalidEmail configuration option, which is enabled by default and protects the API route against this, did not apply to these routes. This issue has been patched in versions 8.6.51 and 9.6.0-alpha.40. The advisory is available at github.com. This vulnerability was named CVE-2026-33323 since 03/18/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1592 by the MITRE ATT&CK project. Upgrading to version 8.6.51 or 9.6.0-alpha.40 eliminates this vulnerability. Applying the patch 967aa57732202009b2389ce9ecb3130d53d657e5 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. 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 8.6.34 8.6.35 8.6.36 8.6.37 8.6.38 8.6.39 8.6.40 8.6.41 8.6.42 8.6.43 8.6.44 8.6.45 8.6.46 8.6.47 8.6.48 8.6.49 8.6.50 9.6.0-alpha.0 9.6.0-alpha.1 9.6.0-alpha.2 9.6.0-alpha.3 9.6.0-alpha.4 9.6.0-alpha.5 9.6.0-alpha.6 9.6.0-alpha.7 9.6.0-alpha.8 9.6.0-alpha.9 9.6.0-alpha.10 9.6.0-alpha.11 9.6.0-alpha.12 9.6.0-alpha.13 9.6.0-alpha.14 9.6.0-alpha.15 9.6.0-alpha.16 9.6.0-alpha.17 9.6.0-alpha.18 9.6.0-alpha.19 9.6.0-alpha.20 9.6.0-alpha.21 9.6.0-alpha.22 9.6.0-alpha.23 9.6.0-alpha.24 9.6.0-alpha.25 9.6.0-alpha.26 9.6.0-alpha.27 9.6.0-alpha.28 9.6.0-alpha.29 9.6.0-alpha.30 9.6.0-alpha.31 9.6.0-alpha.32 9.6.0-alpha.33 9.6.0-alpha.34 9.6.0-alpha.35 9.6.0-alpha.36 9.6.0-alpha.37 9.6.0-alpha.38 9.6.0-alpha.39 License open-source Website Product: https://github.com/parse-community/parse-server/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 5.3 VulDB Meta Temp Score: 5.1 VulDB Base Score: 5.3 VulDB Temp Score: 5.1 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Response discrepancy CWE: CWE-204 / CWE-203 / CWE-200 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: parse-server 8.6.51/9.6.0-alpha.40 Patch: 967aa57732202009b2389ce9ecb3130d53d657e5 Timelineinfo 03/18/2026 CVE reserved 03/24/2026 +6 days Advisory disclosed 03/24/2026 +0 days VulDB entry created 03/24/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-h29g-q5c2-9h4f Status: Confirmed CVE: CVE-2026-33323 (🔒) GCVE (CVE): GCVE-0-2026-33323 GCVE (VulDB): GCVE-100-352846 Entryinfo Created: 03/24/2026 20:52 Changes: 03/24/2026 20:52 (70) Complete: 🔍 Cache ID: 99:B31:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸