CVE-2026-33624 | parse-community parse-server up to 8.6.59/9.6.0-alpha.53 toctou (GHSA-2299-ghjr-6vjp)

VDB-352842 · CVE-2026-33624 · GHSA-2299-GHJR-6VJP PARSE-COMMUNITY PARSE-SERVER UP TO 8.6.59/9.6.0-ALPHA.53 TOCTOU HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 2.1 $0-$5k 0.58+ Summaryinfo A vulnerability classified as problematic was found in parse-community parse-server up to 8.6.59/9.6.0-alpha.53. The affected element is an unknown function. The manipulation results in toctou. This vulnerability is reported as CVE-2026-33624. The attack can be launched remotely. No exploit exists. Upgrading the affected component is advised. Detailsinfo A vulnerability was found in parse-community parse-server up to 8.6.59/9.6.0-alpha.53. It has been classified as problematic. Affected is an unknown function. The manipulation with an unknown input leads to a toctou vulnerability. CWE is classifying the issue as CWE-367. The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. This can cause the product to perform invalid actions when the resource is in an unexpected state. This is going to have an impact on integrity. 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.60 and 9.6.0-alpha.54, an attacker who obtains a user's password and a single MFA recovery code can reuse that recovery code an unlimited number of times by sending concurrent login requests. This defeats the single-use design of recovery codes. The attack requires the user's password, a valid recovery code, and the ability to send concurrent requests within milliseconds. This issue has been patched in versions 8.6.60 and 9.6.0-alpha.54. The advisory is available at github.com. This vulnerability is traded as CVE-2026-33624 since 03/23/2026. The exploitability is told to be difficult. It is possible to launch the attack remotely. Additional levels of successful authentication are required for exploitation. The technical details are unknown and an exploit is not available. Upgrading to version 8.6.60 or 9.6.0-alpha.54 eliminates this vulnerability. Applying the patch 5e70094250a36bfcc14ecd49592be2b94fba66ff 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 8.6.54 8.6.55 8.6.56 8.6.57 8.6.58 8.6.59 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 9.6.0-alpha.43 9.6.0-alpha.44 9.6.0-alpha.45 9.6.0-alpha.46 9.6.0-alpha.47 9.6.0-alpha.48 9.6.0-alpha.49 9.6.0-alpha.50 9.6.0-alpha.51 9.6.0-alpha.52 9.6.0-alpha.53 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: 2.2 VulDB Meta Temp Score: 2.1 VulDB Base Score: 2.2 VulDB Temp Score: 2.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: Toctou CWE: CWE-367 / CWE-362 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.60/9.6.0-alpha.54 Patch: 5e70094250a36bfcc14ecd49592be2b94fba66ff Timelineinfo 03/23/2026 CVE reserved 03/24/2026 +1 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-2299-ghjr-6vjp Status: Confirmed CVE: CVE-2026-33624 (🔒) GCVE (CVE): GCVE-0-2026-33624 GCVE (VulDB): GCVE-100-352842 Entryinfo Created: 03/24/2026 20:49 Changes: 03/24/2026 20:49 (68) Complete: 🔍 Cache ID: 99:755:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸