# CVE-2026-121415: Parse Server before 8.6.111 and 9.0.0 before 9.10.6-alpha.3 Field Corruption via Null Dot Notation Key


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-655c-2xf3-77x9, GHSA-gv55-crjh-3f3x

## What is CVE-2026-121415?

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

### Official description

Parse Server before 8.6.111 and 9.0.0 before 9.10.6-alpha.3 on MongoDB skips field type validation for null-valued dot notation keys, allowing sub-documents to be written beneath Pointer, Number, String, Date, or Boolean fields. Any client with write access, including unauthenticated clients where public writes are permitted, can corrupt field values, make objects unreadable via internal date fields, or break atomic operations on number fields.

Weakness: CWE-20 (Improper Input Validation)

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

2 open source packages ship an affected version, including parse-server.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `parse-server` | npm | `pkg:npm/parse-server` | All versions | 8.6.111 |
| `parse-server` | npm | `pkg:npm/parse-server` | From 9.0.0 | 9.10.6-alpha.3 |

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

Upgrade parse-server to a fixed version for your release line: 9.10.6-alpha.3 or 8.6.111.

## Is CVE-2026-121415 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- parse-server (npm): affected all versions; fixed in 8.6.111
- parse-server (npm): affected from 9.0.0; fixed in 9.10.6-alpha.3

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-121415/ (Markdown: https://insights.sbomify.com/CVE-2026-121415/index.md)
```

## Sources

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

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