CVE-2026-33429 | parse-community parse-server up to 8.6.53/9.6.0-alpha.42 information exposure (GHSA-qpc3-fg4j-8hgm)

VDB-352833 · CVE-2026-33429 · GHSA-QPC3-FG4J-8HGM PARSE-COMMUNITY PARSE-SERVER UP TO 8.6.53/9.6.0-ALPHA.42 INFORMATION EXPOSURE 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.53/9.6.0-alpha.42. It has been classified as problematic. This affects an unknown function. Performing a manipulation results in information exposure. This vulnerability was named CVE-2026-33429. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is recommended. Detailsinfo A vulnerability was found in parse-community parse-server up to 8.6.53/9.6.0-alpha.42. It has been classified as problematic. This affects an unknown code block. The manipulation with an unknown input leads to a information exposure vulnerability. CWE is classifying the issue as CWE-203. The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not. This is going to have an impact on 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 versions 8.6.54 and 9.6.0-alpha.43, an attacker can subscribe to LiveQuery with a watch parameter targeting a protected field. Although the protected field value is properly stripped from event payloads, the presence or absence of update events reveals whether the protected field changed, creating a binary oracle. For boolean protected fields, the timing of change events is equivalent to knowing the field value. This issue has been patched in versions 8.6.54 and 9.6.0-alpha.43. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-33429 since 03/19/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue. Upgrading to version 8.6.54 or 9.6.0-alpha.43 eliminates this vulnerability. Applying the patch 0c0a0a5a37ca821d2553119f2cb3be35322eda4b 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 8.6.51 8.6.52 8.6.53 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 9.6.0-alpha.40 9.6.0-alpha.41 9.6.0-alpha.42 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: Information exposure CWE: CWE-203 / CWE-200 / CWE-284 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.54/9.6.0-alpha.43 Patch: 0c0a0a5a37ca821d2553119f2cb3be35322eda4b Timelineinfo 03/19/2026 CVE reserved 03/24/2026 +5 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-qpc3-fg4j-8hgm Status: Confirmed CVE: CVE-2026-33429 (🔒) GCVE (CVE): GCVE-0-2026-33429 GCVE (VulDB): GCVE-100-352833 Entryinfo Created: 03/24/2026 20:46 Changes: 03/24/2026 20:46 (69) Complete: 🔍 Cache ID: 99:CB9:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸