cve.bz

CVE-2026-32878 parseplatform parse-server: Prototype Pollution

5.3 mediumEPSS 0.4%Fix available

Medium (5.3) in parseplatform parse-server. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in parse-server 8.6.44, 9.6.0-alpha.20.

On this page
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.

Severity

CVSS 4.0

5.3 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 35th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-03-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-1321 Improperly Controlled Modification of Object Prototype Attributes (Prototype Pollution)
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-32878 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-32878?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-32878?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-32878 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
parseplatform:parse-serverbefore 8.6.44
parseplatform:parse-serverfrom 9.0.0 before 9.6.0
parseplatform:parse-server9.6.0:alpha1
parseplatform:parse-server9.6.0:alpha10
parseplatform:parse-server9.6.0:alpha11
parseplatform:parse-server9.6.0:alpha12
parseplatform:parse-server9.6.0:alpha13
parseplatform:parse-server9.6.0:alpha14
parseplatform:parse-server9.6.0:alpha15
parseplatform:parse-server9.6.0:alpha16
parseplatform:parse-server9.6.0:alpha17
parseplatform:parse-server9.6.0:alpha18
parseplatform:parse-server9.6.0:alpha19
parseplatform:parse-server9.6.0:alpha2
parseplatform:parse-server9.6.0:alpha3
parseplatform:parse-server9.6.0:alpha4
parseplatform:parse-server9.6.0:alpha5
parseplatform:parse-server9.6.0:alpha6
parseplatform:parse-server9.6.0:alpha7
parseplatform:parse-server9.6.0:alpha8
parseplatform:parse-server9.6.0:alpha9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-9ccr-fpp6-78qfnpmparse-server>=9.0.0 <9.6.0-alpha.209.6.0-alpha.20
GHSA-9ccr-fpp6-78qfnpmparse-server<8.6.448.6.44

Attack patterns (CAPEC)

  • CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs Likelihood: High · Severity: High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-180 Exploiting Incorrectly Configured Access Control Security Levels Likelihood: High · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON