Servers and applications
GHSA-jvx3-mjpw-r4gh
Missing authorization on Flowise upsert-history endpoints allows authenticated users and API keys to read and delete arbitrary document-store upsert history across workspaces
- Severity
- High 7.7
- Published
- 10 Sept 2026
- Last changed
- 10 Sept 2026
- Added to UpHeron
- 1 Nov 2026
- Weakness
- Authorization bypass through a user-controlled key (IDOR) (CWE-639)Missing authorization (CWE-862)
- Attack
- Over the network · Only under certain conditions · Needs a user account · No user action needed
- Attacker can
- Read data · Change data · Take it down
- CVSS vector
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- Sources
- Project advisories (GitHub)
Description
Flowise exposes GET /api/v1/upsert-history/:id and PATCH /api/v1/upsert-history without any route-level permission checks. The backing service also performs no workspace or ownership validation. It reads history rows by attacker-supplied chatflowid and deletes history rows by attacker-supplied UUID array only.
This is not a harmless metadata leak. UpsertHistory stores parsed result data and flowData snapshots for document-store upsert operations. flowData is built from embedding, record manager, and vector store node configurations, including per-node paramValues. As a result, an authenticated low-privilege user or API key can retrieve or delete arbitrary document-store upsert history outside their permission scope, and the lack of workspace scoping makes cross-workspace access possible whenever a target chatflowId is known.
I reviewed the current Flowise HEAD:
- Version: 3.1.1
- Commit: 2555f10c11fcf0115b5fc2ff3230976abe462623
- Verified date: 2026-04-07
Relevant code paths:
Affected software
| Software | Affected versions |
|---|---|
FlowiseServers and applications · github:flowiseai/flowise |
|
About Flowise
Build AI Agents, Visually
- Archived
- Yes, no longer maintainedGitHub
- Weekly downloads (npm)
- 6,604npm, 15 Nov 2026
- Docker Hub pulls
- 7,390,661Docker Hub, 15 Nov 2026
- GitHub stars
- 55,573GitHub, 15 Nov 2026
- Forks
- 25,094GitHub, 15 Nov 2026
- Latest release
- [email protected]GitHub, 15 Nov 2026
- Released
- 29 Jul 2026GitHub
- First published on GitHub
- 31 Mar 2023GitHub
Source code Website Docker image Package
Vulnerabilities in Flowise
- In our list
- 171
- Published in the last 12 months
- 149
- Critical, last 12 months
- 41
- High, last 12 months
- 70
- Known exploited
- 0
- CVE-2026-130796Flowise 3.1.3 through 3.1.4 MCP Server Token Disclosure via Public Chatflow EndpointHigh 8.8 17 Nov 2026
- CVE-2026-130615Flowise through 3.1.4 SSRF via DNS Rebinding in Playwright and Puppeteer LoadersHigh 7.6 17 Nov 2026
- CVE-2026-127214Flowise 3.1.4 SSRF Bypass via Custom Function SandboxMedium 6.3 13 Nov 2026
- CVE-2026-119978Flowise through 3.1.4 Custom Function Sandbox Escape RCE via LocalFileStoreCritical 9.0 30 Oct 2026
- CVE-2026-90580A vulnerability was found in FlowiseAI Flowise up to 3.0.2. This vulnerability affects the function axios.post of the file packages/server/src/controllers/evaluations/index.ts of the component Evaluations Endpoint. The manipulation of the argument Host/X-Forwarded-Proto results in server-side request forgery. The attack may be launched remotely. The exploit has been made public and could be…Low 2.1 13 Sept 2026
- CVE-2026-90535Flowise versions before 3.1.4 contain an unauthenticated denial of service vulnerability in the /api/v1/text-to-speech/abort endpoint that accepts user-supplied chatflowId and chatId without ownership verification. Attackers can terminate active chatflow predictions for any user by submitting requests with known chatflow and chat identifiers, causing targeted service disruption.Medium 6.3 12 Sept 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-jvx3-mjpw-r4gh
- github.com https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-jvx3-mjpw-r4gh