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.20 and 8.6.44, an attacker can bypass the default request keyword denylist protection and the class-level permission for adding fields by sending a crafted request that exploits prototype pollution in the deep copy mechanism. This allows injecting fields into class schemas that have field addition locked down, and can cause permanent schema type conflicts that cannot be resolved even with the master key. In 9.6.0-alpha.20 and 8.6.44, the vulnerable third-party deep copy library has been replaced with a built-in deep clone mechanism that handles prototype properties safely, allowing the existing denylist check to correctly detect and reject the prohibited keyword. No known workarounds are available.
References
| Link | Resource |
|---|---|
| https://github.com/parse-community/parse-server/pull/10200 | Issue Tracking |
| https://github.com/parse-community/parse-server/pull/10201 | Issue Tracking |
| https://github.com/parse-community/parse-server/security/advisories/GHSA-9ccr-fpp6-78qf | Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2026-03-18 22:16
Updated : 2026-03-19 17:28
NVD link : CVE-2026-32878
Mitre link : CVE-2026-32878
CVE.ORG link : CVE-2026-32878
JSON object : View
Products Affected
parseplatform
- parse-server
CWE
CWE-1321
Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')