CVE-2026-30938 json
Parse Server has denylist `requestKeywordDenylist` keyword scan bypass through nested object placement
published 2026-03-10 8 mo ago modified 2026-09-08 2 mo ago also BIT-parse-2026-30938 , EUVD-2026-10547 , GHSA-q342-9w2p-57fp
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 39%
- 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 8.6.12 and 9.5.1-alpha.1, the requestKeywordDenylist security control can be bypassed by placing any nested object or array before a prohibited keyword in the request payload. This is caused by a logic bug that stops scanning sibling keys after encountering the first nested value. Any custom requestKeywordDenylist entries configured by the developer are equally by-passable using the same technique. All Parse Server deployments are affected. The requestKeywordDenylist is enabled by default. This vulnerability is fixed in 8.6.12 and 9.5.1-alpha.1. Use a Cloud Code beforeSave trigger to validate incoming data for prohibited keywords across all classes.
Patch / fix
- npm parse-server 8.6.12, 9.5.1-alpha.1
- bitnami parse 8.6.12, 9.5.1
- parseplatform parse-server 8.6.12, 9.5.1-alpha.1
- parseplatform parse_server 8.6.12, 9.5.1-alpha.1
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 8 mo ago
Exploit prediction
0.46% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N |
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/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:X |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | parse-server | <8.6.12 >=9.0.0-alpha.1, <9.5.1-alpha.1 |
8.6.12 9.5.1-alpha.1 |
| bitnami | parse | <8.6.12 >=9.0.0, <9.5.1 |
8.6.12 9.5.1 |
Affected products
- parse-community parse-server
Classification
- Weakness
-
- CWE-693 Protection Mechanism Failure
References
-
github.com
/parse-community/parse-server/security/advisories/GHSA-q342-9w2p-57fp
web, mitigation, patch, vendor-advisory, advisory
-
github.com
/parse-community/parse-server/releases/tag/8.6.12
web, product, release-notes, article
-
github.com
/parse-community/parse-server/releases/tag/9.5.1-alpha.1
web, product, release-notes, article
-
nvd.nist.gov
/vuln/detail/CVE-2026-30938
advisory, web
-
github.com
/parse-community/parse-server
package
Sources
- CVE List CVE-2026-30938
- GitHub Advisory GHSA-q342-9w2p-57fp
- NVD CVE-2026-30938
- OSV BIT-parse-2026-30938
Fencer Vulns 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.