CVE-2026-33627 | parse-community parse-server up to 8.6.60/9.6.0-alpha.54 Endpoint information disclosure (GHSA-37mj-c2wf-cx96)
VulDBArchived Mar 24, 2026✓ Full text saved
A vulnerability categorized as problematic has been discovered in parse-community parse-server up to 8.6.60/9.6.0-alpha.54 . This vulnerability affects unknown code of the component Endpoint . Such manipulation leads to information disclosure. This vulnerability is referenced as CVE-2026-33627 . It is possible to launch the attack remotely. No exploit is available. It is advisable to upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-352851 · CVE-2026-33627 · GHSA-37MJ-C2WF-CX96
PARSE-COMMUNITY PARSE-SERVER UP TO 8.6.60/9.6.0-ALPHA.54 ENDPOINT INFORMATION DISCLOSURE
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
4.1 $0-$5k 0.96+
Summaryinfo
A vulnerability identified as problematic has been detected in parse-community parse-server up to 8.6.60/9.6.0-alpha.54. This issue affects some unknown processing of the component Endpoint. Performing a manipulation results in information disclosure. This vulnerability is identified as CVE-2026-33627. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.
Detailsinfo
A vulnerability was found in parse-community parse-server up to 8.6.60/9.6.0-alpha.54. It has been classified as problematic. This affects some unknown functionality of the component Endpoint. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. 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.61 and 9.6.0-alpha.55, an authenticated user calling GET /users/me receives unsanitized auth data, including sensitive credentials such as MFA TOTP secrets and recovery codes. The endpoint internally uses master-level authentication for the session query, and the master context leaks through to the user data, bypassing auth adapter sanitization. An attacker who obtains a user's session token can extract MFA secrets to generate valid TOTP codes indefinitely. This issue has been patched in versions 8.6.61 and 9.6.0-alpha.55.
The weakness was released by The Master as GHSA-37mj-c2wf-cx96. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-33627 since 03/23/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. 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.61 or 9.6.0-alpha.55 eliminates this vulnerability. Applying the patch 5b8998e6866bcf75be7b5bb625e27d23bfaf912c 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
8.6.60
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
9.6.0-alpha.54
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: Information disclosure
CWE: CWE-200 / CWE-284 / 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.61/9.6.0-alpha.55
Patch: 5b8998e6866bcf75be7b5bb625e27d23bfaf912c
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-37mj-c2wf-cx96
Researcher: The Master
Status: Confirmed
CVE: CVE-2026-33627 (🔒)
GCVE (CVE): GCVE-0-2026-33627
GCVE (VulDB): GCVE-100-352851
Entryinfo
Created: 03/24/2026 20:53
Changes: 03/24/2026 20:53 (71)
Complete: 🔍
Cache ID: 99:A10:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸