GHSA-GGGP-6QMF-XWWC
openai-realtime endpoints allow cross-workspace tool disclosure and execution via unscoped chatflow ID
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
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche 3.1.4 | flowise · -33 d desde divulgación | |
| Divulgación | Publicada | GHSA-GGGP-6QMF-XWWC divulgada · CVSS 7.6 (GitHub) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
`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.
Details
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. No ownership check is enforced before the victim flow is resolved and its tools are initialized.
As a result:
- `GET /api/v1/openai-realtime/:id` returns the victim agent's tool definitions
- `POST /api/v1/openai-realtime/:id` invokes the selected victim tool and returns its output
Affected components:
- `packages/server/src/routes/openai-realtime/index.ts`
- `packages/server/src/services/openai-realtime/index.ts`
Relevant code references:
- `packages/server/src/routes/openai-realtime/index.ts:6-9`
- `packages/server/src/services/openai-realtime/index.ts:8-12`
- `packages/server/src/services/openai-realtime/index.ts:43-75`
- `packages/server/src/services/openai-realtime/index.ts:84-107`
- `packages/server/src/services/openai-realtime/index.ts:129-132`
- `packages/server/src/services/openai-realtime/index.ts:142-161`
Tested version:
- Flowise `3.1.2`
- Tested commit: `ea68f9a859a9b04fa7ae732e8d878e75fd81d5c7`
Proof of Concept (PoC)
Environment
- Workspace `A`: `2716cca9-4087-409b-8cc6-a87d9beb6e5b`
- Workspace `B`: `15caa1b6-9ebb-41a3-a8cc-2470ff18ca05`
- Workspace `A` API key ID: `aab1c1a30d62d37fe484`
- Victim flow UUID: `fee33ded-9094-42c5-b83e-ddd9f61b21ec`
Ownership Proof (Database)
apikey/workspace:
('aab1c1a30d62d37fe484', 'CVE PoC Workspace A', '2716cca9-4087-409b-8cc6-a87d9beb6e5b', 'Workspace A')
chatflows/workspace:
('fee33ded-9094-42c5-b83e-ddd9f61b21ec', 'Victim Tool Agent', '15caa1b6-9ebb-41a3-a8cc-2470ff18ca05', 'Workspace B')
````
#### Step 1 – Cross-Workspace Tool Disclosure
```http
GET /api/v1/openai-realtime/fee33ded-9094-42c5-b83e-ddd9f61b21ec HTTP/1.1
Authorization: Bearer <Workspace A API key>HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8[
{
"name": "calculator",
"description": "Useful for getting the result of a math expression. The input to this tool should be a valid mathematical expression that could be executed by a simple calculator.",
"parameters": {
"type": "object",
"properties": {
"input": {
"type": "string"
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
}
]Step 2 – Cross-Workspace Tool Execution
POST /api/v1/openai-realtime/fee33ded-9094-42c5-b83e-ddd9f61b21ec HTTP/1.1
Authorization: Bearer <Workspace A API key>
Content-Type: application/json
{"chatId":"poc-chat-a-001","toolName":"calculator","inputArgs":{"input":"6*7"}}HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8{
"output": "42",
"sourceDocuments": [],
"artifacts": []
}This proves that a credential from Workspace `A` can disclose and invoke tools attached to a `ChatFlow` owned by Workspace `B`.
Expected behavior:
The server should reject requests for `ChatFlow` objects outside the caller's workspace.
Actual behavior:
The server resolves the victim `ChatFlow` and executes its tool based solely on the supplied `chatflowid`.
Impact
An authenticated attacker within the same Flowise organization can:
- Enumerate tools configured on another workspace's `ChatFlow`
- Execute tools belonging to a different workspace
- Retrieve tool outputs, including computation results, source documents, and artifacts
- Trigger unintended side effects on external integrations configured in the victim workspace
This vulnerability breaks workspace isolation and permits unauthorized cross-workspace access to protected `ChatFlow` runtime objects and associated tool execution surfaces.
Root Cause
The API does not enforce workspace-level authorization when resolving `chatflowid`, loading `ChatFlow` configuration, or executing associated tools. The runtime trusts the provided identifier without verifying ownership.
Remediation
- Enforce strict workspace ownership validation before loading a `ChatFlow`
- Reject any `chatflowid` not belonging to the caller’s workspace
- Apply consistent authorization checks on both GET and POST endpoints
- Ensure tool execution is strictly scoped to the authenticated workspace context
Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
npmflowise |
Corregida | 3.1.4 | -33 d | 3.1.4 no afectada |
3.1.4Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-gggp-6qmf-xwwcLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
