parse-community parse-server up to 8.6.74 Endpoint /sessions/ authorization

Summaryinfo

A vulnerability marked as problematic has been reported in parse-community parse-server up to 8.6.74. The affected element is an unknown function of the file /sessions/ of the component Endpoint. This manipulation causes authorization. This vulnerability appears as CVE-2026-39381. The attack may be initiated remotely. There is no available exploit. 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.74. Affected by this vulnerability is an unknown code of the file /sessions/ of the component Endpoint. 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 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 9.8.0-alpha.7 and 8.6.75, the GET /sessions/me endpoint returns _Session fields that the server operator explicitly configured as protected via the protectedFields server option. Any authenticated user can retrieve their own session's protected fields with a single request. The equivalent GET /sessions and GET /sessions/:objectId endpoints correctly strip protected fields. This vulnerability is fixed in 9.8.0-alpha.7 and 8.6.75.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-39381 since 04/07/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available.

Upgrading to version 8.6.75 or 9.8.0-alpha.7 eliminates this vulnerability. Applying a patch 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.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-19917). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

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
• 8.6.61
• 8.6.62
• 8.6.63
• 8.6.64
• 8.6.65
• 8.6.66
• 8.6.67
• 8.6.68
• 8.6.69
• 8.6.70
• 8.6.71
• 8.6.72
• 8.6.73
• 8.6.74

Website

• Product: https://github.com/parse-community/parse-server/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion