# CVE-2026-121965: Parse Server before 8.6.113 and 9.10.6-alpha.5 Prototype Pollution via Dot Notation Key


- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 4 Nov 2026
- **Also known as:** GHSA-95hp-82c6-25q5, GHSA-vx56-7cxr-7m5w

## What is CVE-2026-121965?

CVE-2026-121965 is a medium-severity vulnerability in parse-community parse-server, published on 4 Nov 2026. 

### Official 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.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2026-121965?


## How do I fix CVE-2026-121965?

No fix has been published for CVE-2026-121965 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-121965 being exploited?

There is no known exploitation of CVE-2026-121965 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-121965 and fix it if it is affected.

What it is: CVE-2026-121965 is a medium-severity vulnerability in parse-community parse-server, published on 4 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121965 in the wild and no public exploit code.

Affected product: parse-community parse-server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-121965/ (Markdown: https://insights.sbomify.com/CVE-2026-121965/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-121965
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-121965
- OSV: https://osv.dev/vulnerability/CVE-2026-121965

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-121965/
Summaries are generated and may contain mistakes; the official description above is the record.