parse-community parse-server up to 8.6.10/9.0.0 9.5.0-alpha.13 regex redos
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in parse-community parse-server up to 8.6.10/9.0.0 9.5.0-alpha.13 and classified as problematic. Affected is an unknown function. The manipulation of the argument regex results in redos. This vulnerability is known as CVE-2026-30925. It is possible to launch the attack remotely. No exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in parse-community parse-server up to 8.6.10/9.0.0 9.5.0-alpha.13. Affected is an unknown code. The manipulation of the argument regex with an unknown input leads to a redos vulnerability. CWE is classifying the issue as CWE-1333. The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles. This is going to have an impact on availability. CVE summarizes:
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.5.0-alpha.14 and 8.6.11, a malicious client can subscribe to a LiveQuery with a crafted $regex pattern that causes catastrophic backtracking, blocking the Node.js event loop. This makes the entire Parse Server unresponsive, affecting all clients. Any Parse Server deployment with LiveQuery enabled is affected. The attacker only needs the application ID and JavaScript key, both of which are public in client-side apps. This only affects LiveQuery subscription matching, which evaluates regex in JavaScript on the Node.js event loop. Normal REST and GraphQL queries are not affected because their regex is evaluated by the database engine. This vulnerability is fixed in 9.5.0-alpha.14 and 8.6.11.
The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-30925 since 03/07/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1449.003.
Upgrading to version 8.6.11 or 9.0.0 9.5.0-alpha.14 eliminates this vulnerability.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
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
- 9.0.0 9.5.0-alpha.0
- 9.0.0 9.5.0-alpha.1
- 9.0.0 9.5.0-alpha.2
- 9.0.0 9.5.0-alpha.3
- 9.0.0 9.5.0-alpha.4
- 9.0.0 9.5.0-alpha.5
- 9.0.0 9.5.0-alpha.6
- 9.0.0 9.5.0-alpha.7
- 9.0.0 9.5.0-alpha.8
- 9.0.0 9.5.0-alpha.9
- 9.0.0 9.5.0-alpha.10
- 9.0.0 9.5.0-alpha.11
- 9.0.0 9.5.0-alpha.12
- 9.0.0 9.5.0-alpha.13
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.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: 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.11/9.0.0 9.5.0-alpha.14
Timeline
03/07/2026 CVE reserved03/10/2026 Advisory disclosed
03/10/2026 VulDB entry created
03/13/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-30925 (🔒)
GCVE (CVE): GCVE-0-2026-30925
GCVE (VulDB): GCVE-100-349920
Entry
Created: 03/10/2026 07:29Updated: 03/13/2026 01:46
Changes: 03/10/2026 07:29 (67), 03/13/2026 01:46 (12)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.