Parse Server before 8.6.113 and 9.10.6-alpha.5 Prototype Pollution via Dot Notation Key
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 9.10.6-alpha.5, 8.6.113
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 9.10.6-alpha.5, 8.6.113.
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Data gap: No advisory context yet
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity6/10CVSS 6.0
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
CVE-2026-121965 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.0 (medium) and affects parse-server; fixed in 9.10.6-alpha.5 and 8.6.113.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 9/100 · provisional
- Fix
- Fixed in 9.10.6-alpha.5, 8.6.113
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Parse Server, a Node.js backend framework, is affected by a prototype pollution flaw in how it builds objects for Cloud Code triggers and LiveQuery. An attacker over the network with low-privilege login (write access to an object in a class that has a trigger or LiveQuery) can corrupt a built-in function, causing unrelated requests to fail until the server restarts and denying service to all clients and hosted applications.
Read the original description
Parse Server before 8.6.113 and 9.0.0 before 9.10.6-alpha.5 contains a prototype pollution vulnerability when building objects for Cloud Code triggers and LiveQuery, where a dot notation key whose intermediate segment resolves through an inherited member writes onto a process-wide built-in. Clients with write access to an object in a class with a trigger or LiveQuery can corrupt a built-in function, making unrelated requests fail until restart and denying service to all clients and hosted applications.
What to do
Upgrade to a fixed version: 9.10.6-alpha.5, 8.6.113.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- parse-community parse-server
From 9.0.0 · fixed in 9.10.6-alpha.5
- parse-community parse-server
fixed in 8.6.113
Evidence 4
- Advisory
- Patch
- Patch
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121965
Is CVE-2026-121965 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-121965?
parse-server: from 9.0.0 before 9.10.6-alpha.5. parse-server: before 8.6.113.Source: cve.now feed data
How do I fix CVE-2026-121965?
Upgrade to a fixed version: 9.10.6-alpha.5, 8.6.113.Source: cve.now feed data