CVE-2026-30938
published 2026-03-10CVE-2026-30938: 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…
PriorityP433medium5.3CVSS 3.1
AVNACLPRNUINSUCNILAN
EPSS
0.39%
31.1th percentile
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.
Affected
6 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| parse-community | parse-server | < 8.6.12 | 8.6.12 |
| parse-community | parse-server | — | — |
| parse-community | parse-server | >= 0 < 8.6.12 | 8.6.12 |
| parse-community | parse-server | >= 9.0.0-alpha.1 < 9.5.1-alpha.1 | 9.5.1-alpha.1 |
| parseplatform | parse-server | < 8.6.12 | 8.6.12 |
| parseplatform | parse-server | >= 9.0.0 < 9.5.1 | 9.5.1 |
CVSS provenance
nvdv3.15.3MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
nvdv4.06.9MEDIUMCVSS: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
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
Parse Server has denylist `requestKeywordDenylist` keyword scan bypass through nested object placement
ghsa·2026-03-10
CVE-2026-30938 [MEDIUM] CWE-693 Parse Server has denylist `requestKeywordDenylist` keyword scan bypass through nested object placement
Parse Server has denylist `requestKeywordDenylist` keyword scan bypass through nested object placement
### Impact
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.
### Patches
The fix replaces the recursive object scanner with an iterative stack-based traversal that processes all nested values without prematurely exiting the scan loop. This also eliminates a potential
OSV
Parse Server has denylist `requestKeywordDenylist` keyword scan bypass through nested object placement
osv·2026-03-10
CVE-2026-30938 [MEDIUM] Parse Server has denylist `requestKeywordDenylist` keyword scan bypass through nested object placement
Parse Server has denylist `requestKeywordDenylist` keyword scan bypass through nested object placement
### Impact
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.
### Patches
The fix replaces the recursive object scanner with an iterative stack-based traversal that processes all nested values without prematurely exiting the scan loop. This also eliminates a potential
No detection rules found.
No public exploits indexed.
2026-03-10
Published