CVE-2026-32770 json
Parse Server: LiveQuery subscription with invalid regular expression crashes server
published 7mo ago modified 2mo ago also BIT-parse-2026-32770 , EUVD-2026-12985 , GHSA-827p-g5x5-h86c
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
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.19 and 8.6.43, a remote attacker can crash the Parse Server by subscribing to a LiveQuery with an invalid regular expression pattern. The server process terminates when the invalid pattern reaches the regex engine during subscription matching, causing denial of service for all connected clients. The fix in 9.6.0-alpha.19 and 8.6.43 validates regular expression patterns at subscription time, rejecting invalid patterns before they are stored. Additionally, a defense-in-depth try-catch prevents any subscription matching error from crashing the server process. As a workaround, disable LiveQuery if it is not needed.
Patch / fix
- npm parse-server 8.6.43, 9.6.0-alpha.19
- bitnami parse 8.6.43, 9.6.0
- parseplatform parse-server 8.6.43, 9.6.0-alpha.19
- parseplatform parse_server 8.6.43, 9.6.0-alpha.19
- github.com/parse-community/parse-server#10197 pull request
- github.com/parse-community/parse-server#10199 pull request
Is CVE-2026-32770 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7mo ago
Exploit prediction
0.58% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | parse-server | >=9.0.0, <9.6.0-alpha.19 <8.6.43 |
9.6.0-alpha.19 8.6.43 |
| bitnami | parse | <8.6.43 >=9.0.0, <9.6.0 |
8.6.43 9.6.0 |
Affected products
- parse-community parse-server
Classification
- Weakness
-
- CWE-248 Uncaught Exception
References
-
github.com
/parse-community/parse-server/pull/10197
web, issue-tracking, report
-
github.com
/parse-community/parse-server/pull/10199
web, issue-tracking, report
-
github.com
/parse-community/parse-server/security/advisories/GHSA-827p-g5x5-h86c
web, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-32770
advisory, web
-
github.com
/parse-community/parse-server
package
Sources
- CVE List CVE-2026-32770
- GitHub Advisory GHSA-827p-g5x5-h86c
- NVD CVE-2026-32770
- OSV BIT-parse-2026-32770
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.