Summaryinfo

A vulnerability categorized as problematic has been discovered in parse-community parse-server up to 8.6.64/9.7.0-alpha.8. This impacts an unknown function. Executing a manipulation can lead to race condition. This vulnerability appears as CVE-2026-34363. The attack may be performed from remote. There is no available exploit. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in parse-community parse-server up to 8.6.64/9.7.0-alpha.8. It has been declared as problematic. This vulnerability affects an unknown functionality. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. As an impact it is known to affect confidentiality. 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.65 and 9.7.0-alpha.9, when multiple clients subscribe to the same class via LiveQuery, the event handlers process each subscriber concurrently using shared mutable objects. The sensitive data filter modifies these shared objects in-place, so when one subscriber's filter removes a protected field, subsequent subscribers may receive the already-filtered object. This can cause protected fields and authentication data to leak to clients that should not see them, or cause clients that should see the data to receive an incomplete object. Additionally, when an afterEvent Cloud Code trigger is registered, one subscriber's trigger modifications can leak to other subscribers through the same shared mutable state. Any Parse Server deployment using LiveQuery with protected fields or afterEvent triggers is affected when multiple clients subscribe to the same class. This issue has been patched in versions 8.6.65 and 9.7.0-alpha.9.

The advisory is available at github.com. This vulnerability was named CVE-2026-34363 since 03/27/2026. The exploitation appears to be easy. The attack can be initiated remotely. The technical details are unknown and an exploit is not available.

Upgrading to version 8.6.65 or 9.7.0-alpha.9 eliminates this vulnerability. Applying the patch 5834e29234593addaa0251a85f572ad4f376320b 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.

Once again VulDB remains the best source for vulnerability data.

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
• 9.7.0-alpha.0
• 9.7.0-alpha.1
• 9.7.0-alpha.2
• 9.7.0-alpha.3
• 9.7.0-alpha.4
• 9.7.0-alpha.5
• 9.7.0-alpha.6
• 9.7.0-alpha.7
• 9.7.0-alpha.8

License

• open-source

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

Discussion