llamaCVEVulnerability Intelligence
/
Advisory · GitHub · npm · flowise

GHSA-PPMG-4CX6-95HH

Missing authorization on Flowise chat message routes allows low-privileged API keys to read and delete chat history

Sin parche publicado
Descargar PNG JSON
CVSS 4.0
7.5
Alta
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Fuente: GitHub
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
ParcheSin parcheEl fabricante no ha publicado corrección
Exposición70 dDesde la divulgación, 10 sept 2026, 9:18 a. m.
Detección69 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Monitoreo
Detectada +1
10 sept 26
18 nov 26
20 nov 26
10 sept 26
28 sept 26
15 oct 26
2 nov 26
20 nov 26
FechaFaseEventoDetalle
Divulgación Publicada GHSA-PPMG-4CX6-95HH divulgada · CVSS 7.5 (GitHub)
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

Title

Missing RBAC checks on Flowise chat message routes allow low-privileged API keys to read and delete chat history

Description

Flowise `flowise@3.1.2` appears to have missing route-level RBAC checks on chat message read/delete routes.

The global `/api/v1` middleware validates API keys and assigns `req.user.permissions = apiKey.permissions`, but the affected chat message routes call their controllers directly without `checkAnyPermission(...)`.

Affected files:

  • `packages/server/src/routes/chat-messages/index.ts`
  • `packages/server/src/routes/internal-chat-messages/index.ts`

Affected routes:

  • `GET /api/v1/chatmessage/:id`
  • `GET /api/v1/internal-chatmessage/:id`
  • `DELETE /api/v1/chatmessage/:id`

Confirmed affected release:

  • `flowise@3.1.2`
  • tag commit `4114b3b506e7bbee155141175a2ba48e426919dd`

Impact

A valid but low-privileged API key for a workspace can reach chat message read/delete handlers without having the expected flow permissions.

Potential impact:

  • Read chat histories and internal test chat messages for known flow IDs.
  • Access prompts, model responses, source documents, used tools, feedback, and uploaded file metadata serialized in chat messages.
  • Delete chat messages and related uploaded files without flow delete permission.

Suggested CVSS v3.1:

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Estimated severity: High, 8.3.

Affected versions

Confirmed:

  • `flowise@3.1.2`

Broader affected range:

  • Unknown; maintainers should confirm whether earlier RBAC-enabled releases are also affected.

Reproduction steps

  1. Add the test file from the patch package to:
packages/server/src/routes/chat-messages/authorization.test.ts
  1. Before applying the route patch, run:
pnpm --dir packages/server exec jest src/routes/chat-messages/authorization.test.ts --runInBand
  1. Observe insufficient-permission requests return 200 instead of 403.
  1. Apply the route patch.
  1. Run the same test again.
  1. Observe insufficient-permission requests return 403, while requests with `chatflows:view`, `agentflows:view`, or `agentflows:delete` continue to succeed.

Safe PoC

The PoC is a Jest/supertest test with mocked controllers. It uses dummy data only and does not touch real users, credentials, or a database.

Pre-patch observed output:

FAIL src/routes/chat-messages/authorization.test.ts
Tests: 3 failed, 3 passed, 6 total
Expected: 403
Received: 200

Post-patch observed output:

PASS src/routes/chat-messages/authorization.test.ts
Tests: 6 passed, 6 total

I also reproduced the issue against a real local Flowise server with a dummy SQLite database:

Vulnerable local server:
GET /api/v1/chatmessage/:id              -> 200, returned LOCAL_E2E_SECRET_CHAT_CONTENT
GET /api/v1/internal-chatmessage/:id     -> 200, returned LOCAL_E2E_SECRET_CHAT_CONTENT
DELETE /api/v1/chatmessage/:id           -> 200, {"raw":[],"affected":1}

Patched local server:
GET /api/v1/chatmessage/:id              -> 403
GET /api/v1/internal-chatmessage/:id     -> 403
DELETE /api/v1/chatmessage/:id           -> 403
GET /api/v1/chatmessage/:id with allowed key -> 200

The local server E2E used only dummy data and localhost requests.

Patch proposal

Add route-level permission checks:

  • `GET /chatmessage/:id`: `checkAnyPermission('chatflows:view,agentflows:view')`
  • `GET /internal-chatmessage/:id`: `checkAnyPermission('chatflows:view,agentflows:view')`
  • `DELETE /chatmessage/:id`: `checkAnyPermission('chatflows:delete,agentflows:delete')`

Credit request

If this is accepted as a valid vulnerability, please credit GGBoo as the reporter/researcher.

Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.

Vector CVSS 4.0

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · GitHub
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
Requisitos de ataqueAT:P
NingunoPresentes
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:P
NingunaPasivaActiva
Confid. (sistema)VC:H
AltoBajoNinguno
Integridad (sistema)VI:H
AltoBajoNinguno
Disponib. (sistema)VA:H
AltoBajoNinguno
Confid. (posterior)SC:N
AltoBajoNinguno
Integridad (posterior)SI:N
AltoBajoNinguno
Disponib. (posterior)SA:N
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida Última
flowise≤ 3.1.4
3.1.4
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
npmflowise
Sin parche — — 3.1.4 afectada
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Advisoryhttps://github.com/FlowiseAI/Flowise/security/advisories/GHSA-ppmg-4cx6-95hh

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.