CVE-2026-30925
Parseplatform Parse-Server ≤ 8.6.11
Raw vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-30925 is a high-severity Inefficient Regular Expression Complexity (CWE-1333) vulnerability in Parseplatform Parse-Server. Its CVSS base score is 8.2 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-30925 is a denial-of-service vulnerability in Parse Server, an open-source backend deployable on any Node.js infrastructure. Versions prior to 9.5.0-alpha.14 and 8.6.11 are affected when LiveQuery is enabled. The issue stems from a crafted $regex pattern in a LiveQuery subscription that triggers catastrophic backtracking in JavaScript regular expression evaluation on the Node.js event loop, as classified under CWE-1333 (Inefficient Regular Expression Complexity). This contrasts with REST and GraphQL queries, which remain unaffected since their regex handling occurs in the database engine.
Any remote attacker can exploit this vulnerability by subscribing to a LiveQuery using publicly exposed credentials—the application ID and JavaScript key, commonly found in client-side applications. Successful exploitation blocks the Node.js event loop, rendering the entire Parse Server instance unresponsive and impacting all connected clients. The CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) reflects its network accessibility, low complexity, and high availability impact without requiring privileges.
Parse Server advisories and release notes recommend upgrading to version 9.5.0-alpha.14 or 8.6.11, where the vulnerability is fixed. Details are available in the GitHub security advisory (GHSA-mf3j-86qx-cq5j) and release tags for 8.6.11 and 9.5.0-alpha.14.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-10436
Vulnerability Data
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,…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover inefficient regex patterns via performance or static analysis.
Development standards and tools can require safe regex construction and forbid known exponential patterns.
Denial-of-service protections limit resource exhaustion caused by expensive regex evaluation.
Input validation can constrain data that would otherwise trigger worst-case regex complexity.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect and reject regex patterns with exponential worst-case complexity.
Secure development lifecycle mandates review of algorithmic efficiency, directly addressing ReDoS-prone regex.
Application security requirements can specify input-validation rules that limit regex complexity.
Secure architecture principles encourage avoidance of computationally expensive constructs such as catastrophic backtracking.
Secure coding standards explicitly prohibit or limit the use of inefficient regular expressions.