# CVE-2026-100610: Flowise through 3.1.4 Missing Authorization via upsert-history

> Authenticated users can read or delete other users' upsert history and configuration data due to missing authorization checks in Flowise.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-jvx3-mjpw-r4gh, GHSA-r2p4-x7cc-x3mm

## What is CVE-2026-100610?

CVE-2026-100610 is a high-severity missing authorization vulnerability in FlowiseAI Flowise, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Flowise through 3.1.4 exposes GET /api/v1/upsert-history/:id and PATCH /api/v1/upsert-history without route-level permission checks, and the backing service performs no workspace or ownership validation. getAllUpsertHistory() returns UpsertHistory rows selected solely by an attacker-supplied chatflowid, and patchDeleteUpsertHistory() deletes rows by an attacker-supplied array of record UUIDs. As a result, any authenticated low-privilege user or valid API key can read or delete document-store upsert history belonging to other users and other workspaces whenever the target chatflowId (which is exposed publicly in /chatbot/<chatflowId> share links) or row ids are known. The retrievable flowData and result fields contain embedding, record-manager and vector-store node configuration, including per-node paramValues. No patched version is available.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-100610 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100610 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100610 is a high-severity missing authorization vulnerability in FlowiseAI Flowise, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100610 exists.

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

## Sources

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

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