# CVE-2026-103250: n8n before 1.123.80, 2.39.6, and 2.40.1 NoSQL Injection via MongoDB Chat Memory

> Unauthenticated attackers can inject MongoDB operators into the sessionId parameter to read, modify, or delete other users' conversation histories.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-gpvq-4wmp-cp47, GHSA-w24g-6454-7w7f, MINI-hmq4-47w6-cppg

## What is CVE-2026-103250?

CVE-2026-103250 is a high-severity SQL injection vulnerability in n8n-io n8n, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 contain a NoSQL injection vulnerability in the MongoDB Chat Memory node that fails to validate the sessionId parameter. Unauthenticated attackers can supply MongoDB query operators in the sessionId field to access conversation histories from other users and perform unauthorized write and delete operations.

Weakness: CWE-943 (Improper Neutralization of Special Elements in Data Query Logic)

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


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

Upgrade to a fixed version.

## Is CVE-2026-103250 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103250 is a high-severity SQL injection vulnerability in n8n-io n8n, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-103250 in the wild and no public exploit code.

Affected product: n8n-io n8n. 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-103250/ (Markdown: https://insights.sbomify.com/CVE-2026-103250/index.md)
```

## Sources

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

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