Parse Community Parse Server up to 8.6.95/9.10.2-alpha.4 Transactional Batch race condition
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 4.24- |
Summary
A vulnerability, which was classified as critical, was found in Parse Community Parse Server up to 8.6.95/9.10.2-alpha.4. This vulnerability affects unknown code of the component Transactional Batch. Executing a manipulation can lead to race condition. This vulnerability is handled as CVE-2026-109954. The attack can be executed remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability was found in Parse Community Parse Server up to 8.6.95/9.10.2-alpha.4. It has been declared as critical. This vulnerability affects some unknown functionality of the component Transactional Batch. 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 integrity, and availability. CVE summarizes:
Parse Server 5.4.0 before 8.6.96 and 9.0.0 before 9.10.2-alpha.5 shares transactional batch state across concurrent requests, letting any client's transactional batch request interfere with other clients' database writes. On PostgreSQL or MongoDB replica sets and sharded clusters, other clients' acknowledged writes are rolled back if the batch fails, and PostgreSQL transactions can remain open indefinitely, causing subsequent writes to fail.
The advisory is available at github.com. This vulnerability was named CVE-2026-109954 since 10/13/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available.
Upgrading to version 8.6.96 or 9.10.2-alpha.5 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
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
- 8.6.75
- 8.6.76
- 8.6.77
- 8.6.78
- 8.6.79
- 8.6.80
- 8.6.81
- 8.6.82
- 8.6.83
- 8.6.84
- 8.6.85
- 8.6.86
- 8.6.87
- 8.6.88
- 8.6.89
- 8.6.90
- 8.6.91
- 8.6.92
- 8.6.93
- 8.6.94
- 8.6.95
- 9.10.2-alpha.0
- 9.10.2-alpha.1
- 9.10.2-alpha.2
- 9.10.2-alpha.3
- 9.10.2-alpha.4
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 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: 🔍
Exploiting
Class: Race conditionCWE: 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 Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Parse Server 8.6.96/9.10.2-alpha.5
Timeline
10/13/2026 Advisory disclosed10/13/2026 CVE reserved
10/13/2026 VulDB entry created
10/13/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2026-109954 (🔒)
GCVE (CVE): GCVE-0-2026-109954
GCVE (VulDB): GCVE-100-417706
Entry
Created: 10/13/2026 16:23Changes: 10/13/2026 16:23 (76)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.