CVE-2026-33527 | parse-community parse-server up to 8.6.56/9.6.0-alpha.47 REST API authorization (GHSA-jc39-686j-wp6q)

VDB-352852 · CVE-2026-33527 · GHSA-JC39-686J-WP6Q PARSE-COMMUNITY PARSE-SERVER UP TO 8.6.56/9.6.0-ALPHA.47 REST API AUTHORIZATION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 4.1 $0-$5k 0.96+ Summaryinfo A vulnerability labeled as problematic has been found in parse-community parse-server up to 8.6.56/9.6.0-alpha.47. Impacted is an unknown function of the component REST API. Executing a manipulation can lead to authorization. This vulnerability is tracked as CVE-2026-33527. The attack can be launched remotely. No exploit exists. The affected component should be upgraded. Detailsinfo A vulnerability was found in parse-community parse-server up to 8.6.56/9.6.0-alpha.47. It has been declared as problematic. This vulnerability affects an unknown part of the component REST API. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. As an impact it is known to affect 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.57 and 9.6.0-alpha.48, an authenticated user can overwrite server-generated session fields such as expiresAt and createdWith when updating their own session via the REST API. This allows bypassing the server's configured session lifetime policy, making a session effectively permanent. This issue has been patched in versions 8.6.57 and 9.6.0-alpha.48. The advisory is shared for download at github.com. This vulnerability was named CVE-2026-33527 since 03/20/2026. The exploitation appears to be easy. The attack can be initiated remotely. There are neither technical details nor an exploit publicly available. Upgrading to version 8.6.57 or 9.6.0-alpha.48 eliminates this vulnerability. Applying the patch 26b628c8fb3cc79ea955374769eebcff6f8a8a73 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 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 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: 4.3 VulDB Meta Temp Score: 4.1 VulDB Base Score: 4.3 VulDB Temp Score: 4.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: Authorization CWE: CWE-863 / CWE-285 / CWE-266 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.57/9.6.0-alpha.48 Patch: 26b628c8fb3cc79ea955374769eebcff6f8a8a73 Timelineinfo 03/20/2026 CVE reserved 03/24/2026 +4 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-jc39-686j-wp6q Status: Confirmed CVE: CVE-2026-33527 (🔒) GCVE (CVE): GCVE-0-2026-33527 GCVE (VulDB): GCVE-100-352852 Entryinfo Created: 03/24/2026 20:53 Changes: 03/24/2026 20:53 (69) Complete: 🔍 Cache ID: 99:79A:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸