# CVE-2026-119126: Parse Server before 8.6.106 and 9.0.0 before 9.10.5-alpha.7 mishandles dot notation keys with null or undefined values when building the sav


- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-969q-274f-mc7w, GHSA-jqwm-2hj5-gmq3

## What is CVE-2026-119126?

CVE-2026-119126 is a low-severity vulnerability in parse-community parse-server, published on 29 Oct 2026. 

### Official description

Parse Server before 8.6.106 and 9.0.0 before 9.10.5-alpha.7 mishandles dot notation keys with null or undefined values when building the saved object, so a write is stored but returns an error and skips afterSave triggers and LiveQuery events. A client with write access can exploit this to evade audit logging, notifications, and derived data updates.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

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


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

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

## Is CVE-2026-119126 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119126 is a low-severity vulnerability in parse-community parse-server, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119126 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-119126/ (Markdown: https://insights.sbomify.com/CVE-2026-119126/index.md)
```

## Sources

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

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