parse-community parse-server up to 8.6.36/9.0.0 9.6.0-alpha.10 race condition
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in parse-community parse-server up to 8.6.36/9.0.0 9.6.0-alpha.10 and classified as problematic. This affects an unknown part. The manipulation leads to race condition. This vulnerability is traded as CVE-2026-32242. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, has been found in parse-community parse-server up to 8.6.36/9.0.0 9.6.0-alpha.10. This issue affects an unknown part. The manipulation with an unknown input leads to a race condition vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. 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.6.0-alpha.11 and 8.6.37, Parse Server's built-in OAuth2 auth adapter exports a singleton instance that is reused directly across all OAuth2 provider configurations. Under concurrent authentication requests for different OAuth2 providers, one provider's token validation may execute using another provider's configuration, potentially allowing a token that should be rejected by one provider to be accepted because it is validated against a different provider's policy. Deployments that configure multiple OAuth2 providers via the oauth2: true flag are affected. This vulnerability is fixed in 9.6.0-alpha.11 and 8.6.37.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-32242 since 03/11/2026. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 8.6.37 or 9.0.0 9.6.0-alpha.11 eliminates this vulnerability. The upgrade is hosted for download at github.com.
Be aware that VulDB is the high quality source for vulnerability data.
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
- 9.0.0 9.6.0-alpha.0
- 9.0.0 9.6.0-alpha.1
- 9.0.0 9.6.0-alpha.2
- 9.0.0 9.6.0-alpha.3
- 9.0.0 9.6.0-alpha.4
- 9.0.0 9.6.0-alpha.5
- 9.0.0 9.6.0-alpha.6
- 9.0.0 9.6.0-alpha.7
- 9.0.0 9.6.0-alpha.8
- 9.0.0 9.6.0-alpha.9
- 9.0.0 9.6.0-alpha.10
Website
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.4
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.4
NVD Vector: 🔒
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
EPSS Score: 🔒
EPSS Percentile: 🔒
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.37/9.0.0 9.6.0-alpha.11
Timeline
03/11/2026 CVE reserved03/12/2026 Advisory disclosed
03/12/2026 VulDB entry created
03/15/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-2cjm-2gwv-m892
Status: Confirmed
CVE: CVE-2026-32242 (🔒)
GCVE (CVE): GCVE-0-2026-32242
GCVE (VulDB): GCVE-100-350759
Entry
Created: 03/12/2026 21:52Updated: 03/15/2026 02:51
Changes: 03/12/2026 21:52 (67), 03/15/2026 02:51 (12)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.