# CVE-2026-91937: Flowise before 3.1.4 NoSQL Injection via sessionId

> Unauthenticated attackers can read other users' chat history by injecting MongoDB operators into the sessionId parameter in Flowise.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-pcg8-jx3g-5wm7, GHSA-wpvf-4vfx-rgxm

## What is CVE-2026-91937?

CVE-2026-91937 is a high-severity vulnerability in FlowiseAI Flowise, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Flowise before 3.1.4 fails to sanitize the overrideConfig.sessionId parameter before using it in MongoDB queries within the MongoDBMemory node. Unauthenticated attackers can submit MongoDB operator objects through the prediction API to read chat history records belonging to other users from the shared collection.

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

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


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

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

## Is CVE-2026-91937 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-91937 is a high-severity vulnerability in FlowiseAI Flowise, published on 15 Sep 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-91937 in the wild and no public exploit code.

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

## Sources

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

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