Cyber Resilience

CVE-2026-32878

Parseplatform Parse-Server ≤ 8.6.44

Published
18 March 2026
Modified
19 March 2026
Patch / advisory
View advisory
CVSS Score v4 5.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/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
EPSS Score 0.0034 27th percentile
Risk Priority 32 floored blend · peak EPSS

Summary

CVE-2026-32878 is a medium-severity Prototype Pollution (CWE-1321) vulnerability in Parseplatform Parse-Server. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 27th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

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-32878 is a prototype pollution vulnerability in Parse Server, an open source backend deployable on any Node.js infrastructure. In versions prior to 9.6.0-alpha.20 and 8.6.44, the deep copy mechanism used in request processing allows attackers to bypass the default request keyword denylist protection and class-level permissions that restrict field additions. This CWE-1321 issue enables the injection of unauthorized fields into class schemas where additions are locked down, rated at CVSS 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) due to high integrity impact.

Any unauthenticated remote attacker can exploit this by sending a crafted request that pollutes prototypes during deep copying, evading denylist checks. Successful exploitation injects fields into protected schemas, potentially causing permanent schema type conflicts that persist even when using the master key, disrupting data integrity and schema management without requiring privileges.

Parse Server addresses this in versions 9.6.0-alpha.20 and 8.6.44 by replacing the vulnerable third-party deep copy library with a built-in deep clone mechanism that safely handles prototype properties, ensuring the denylist correctly detects and rejects prohibited keywords. No known workarounds exist, as detailed in the project's security advisory (GHSA-9ccr-fpp6-78qf) and related pull requests.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-1321

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1565 Data Manipulation Impact
Adversaries may insert, delete, or manipulate data in order to influence external outcomes or hide activity, thus threatening the integrity of the data.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-36475Same product: Parseplatform Parse-Server
CVE-2026-32886Same product: Parseplatform Parse-Server
CVE-2026-30939Same product: Parseplatform Parse-Server
CVE-2026-31875Same product: Parseplatform Parse-Server
CVE-2023-32689Same product: Parseplatform Parse-Server
CVE-2026-34595Same product: Parseplatform Parse-Server
CVE-2024-29027Same product: Parseplatform Parse-Server
CVE-2024-27298Same product: Parseplatform Parse-Server
CVE-2026-32248Same product: Parseplatform Parse-Server
CVE-2026-30941Same product: Parseplatform Parse-Server

Affected Assets

parseplatform
parse-server
9.6.0 · ≤ 8.6.44 · 9.0.0 — 9.6.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V15.3.6

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and safe property assignment to prevent prototype pollution.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches prototype-pollution flaws before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and object-handling controls that directly prevent prototype pollution.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for safeguards against unsafe object attribute manipulation.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the likelihood of prototype pollution through safe design patterns.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prohibit unsafe prototype attribute assignment and require defensive checks.

A.8.32 Change management partial match
prevents

Change-management processes ensure security fixes for prototype-pollution issues are tracked and deployed.

References