Servers and applications
GHSA-gggp-6qmf-xwwc
openai-realtime endpoints allow cross-workspace tool disclosure and execution via unscoped chatflow ID
- Severity
- High 7.6
- Published
- 31 Aug 2026
- Last changed
- 31 Aug 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 3.1.4
- Weakness
- Information exposure (CWE-200)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 · Slow it down
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N- Sources
- Project advisories (GitHub)
Description
GET /api/v1/openai-realtime/:id and POST /api/v1/openai-realtime/:id in Flowise allow a user or API key from one workspace to disclose and execute tools belonging to a ChatFlow in another workspace by supplying the victim chatflowid directly.
This is not limited to metadata exposure. The POST route reaches real tool execution through the selected victim tool and returns its output. Depending on the configured tools, this can also trigger external side effects.
This constitutes a cross-workspace authorization bypass affecting protected ChatFlow runtime objects and their associated tools.
The openai-realtime routes accept a raw chatflowid and do not perform a resource-level authorization check to ensure that the referenced ChatFlow belongs to the caller's workspace.
The implementation loads the victim ChatFlow directly by ID and reconstructs the runtime context using the victim flow's workspaceId and organization.
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-gggp-6qmf-xwwc
- github.com https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-gggp-6qmf-xwwc