parse-community parse-server up to 8.6.76/9.9.1-alpha.0 request-header Parser redos
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 4.63- |
Summary
A vulnerability, which was classified as problematic, has been found in parse-community parse-server up to 8.6.76/9.9.1-alpha.0. Affected by this issue is some unknown functionality of the component request-header Parser. The manipulation leads to redos. This vulnerability is traded as CVE-2026-47138. It is possible to initiate the attack remotely. There is no exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in parse-community parse-server up to 8.6.76/9.9.1-alpha.0 and classified as problematic. This issue affects an unknown functionality of the component request-header Parser. The manipulation with an unknown input leads to a redos vulnerability. Using CWE to declare the problem leads to CWE-1333. The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles. Impacted is 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 versions 8.6.77 and 9.9.1-alpha.1, an unauthenticated attacker who knows a publicly-known Parse Application ID can submit a single HTTP request whose client SDK version field contains adversarial input that triggers polynomial backtracking in a request-header parser. The parsing runs before session authentication and before rate limiting on every /parse/* request, so the request consumes seconds to minutes of synchronous CPU on a Node.js worker before any access control evaluates it. A small number of concurrent requests can saturate a worker; a single large request via the body-field variant can pin a worker for minutes. Production deployments running the default configuration are affected. This issue has been patched in versions 8.6.77 and 9.9.1-alpha.1.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-47138 since 05/18/2026. The exploitation is known to be easy. 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. The attack technique deployed by this issue is T1449.003 according to MITRE ATT&CK.
Upgrading to version 8.6.77 or 9.9.1-alpha.1 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.
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
- 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
- 9.9.1-alpha
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: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: RedosCWE: CWE-1333 / CWE-400 / CWE-404
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.77/9.9.1-alpha.1
Patch: github.com
Timeline
05/18/2026 CVE reserved06/12/2026 Advisory disclosed
06/12/2026 VulDB entry created
06/12/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-38m6-82c8-4xfm
Status: Confirmed
CVE: CVE-2026-47138 (🔒)
GCVE (CVE): GCVE-0-2026-47138
GCVE (VulDB): GCVE-100-370679
Entry
Created: 06/12/2026 22:30Changes: 06/12/2026 22:30 (69)
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.