CVE-2026-32886: parse-server · Prototype Pollution
Affects parse-serverSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 9.6.0-alpha.24 or 8.6.47 soon.
Data as of 31 Oct 2026, 20:20 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.6.0-alpha.24, 8.6.47
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.
What to do
Upgrade parse-server to 9.6.0-alpha.24 or 8.6.47; parse-server to 8.6.47.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| parse-communityparse-server | Affected
| Fixed in
|
| parse-communityparse-server | Affected
| Fixed in
|
npmparse-serverpkg:npm/parse-serverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The definitive mitigation is to upgrade parse-server to version 9.6.0-alpha.24 or later, or 8.6.47 or later, where the vulnerability is patched. Since no workaround exists, patching is the only reliable defense. Organizations should audit their environments to identify all parse-server instances, especially those exposed to the internet, and prioritize patching. Implement network-level protections such as Web Application Firewalls (WAFs) to detect and block suspicious requests targeting cloud function endpoints with anomalous function names. Employ rate limiting to reduce the risk of repeated exploitation attempts causing denial of service. Monitor server logs for unusual cloud function invocation patterns that may indicate exploitation attempts. Consider isolating parse-server instances behind VPNs or internal networks where possible to reduce exposure. Finally, maintain an incident response plan to quickly recover from potential DoS events caused by this vulnerability.
Description
CVE-2026-32886 is a high-severity prototype pollution vulnerability in parse-community's parse-server versions prior to 9.6.0-alpha.24 and 8.6.47. It allows remote attackers to crash the Parse Server process by invoking a cloud function endpoint with a specially crafted function name that traverses the JavaScript prototype chain, causing a stack overflow. The vulnerability arises from improper control of object prototype attribute modification during cloud function name resolution. The fix restricts property lookups to own properties only, preventing prototype chain traversal. No known workarounds exist, and exploitation requires no authentication or user interaction.