llamaCVEVulnerability Intelligence
/
Advisory · GitHub · npm · flowise

GHSA-7X8X-VV46-4579

Cross-tenant/cross-org authorization gaps in Enterprise role, and SSO-config endpoints

Parche disponible
Descargar PNG JSON
CVSS 4.0
7.6
Alta
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
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versiónPrimer parche a -33 d de la divulgación
Exposición80 dDesde la divulgación, 31 ago 2026, 9:00 a. m.
Detección79 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Parche 3.1.4
Monitoreo
Detectada +1
29 jul 26
31 ago 26
18 nov 26
20 nov 26
29 jul 26
26 ago 26
24 sept 26
22 oct 26
20 nov 26
FechaFaseEventoDetalle
Remediación Parche 3.1.4 flowise · -33 d desde divulgación
Divulgación Publicada GHSA-7X8X-VV46-4579 divulgada · CVSS 7.6 (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

### Summary
Five Enterprise-tier endpoints fetch or mutate a workspace/organization/role by a client-supplied id with no verification that it belongs to the acting user's own org/workspace. All five are gated behind `IdentityManager.checkFeatureByPlan(...)` (a paid-license feature flag) or a hardcoded `assertEnterprisePlatform()` check, so we could not execute them to completion on an unlicensed local instance — the underlying authorization gap is nonetheless confirmed by direct source review, and we are reporting it for maintainers to verify against their own licensed Enterprise test environment. We deliberately did not attempt to work around the license gate or test against Flowise Cloud production, since #1 below is destructive (data deletion) and doing so against real customer data would be irresponsible.

Details

1. `DELETE /api/v1/workspace/{id}` (`enterprise/controllers/workspace.controller.ts:190` → `services/workspace.service.ts:164`, `deleteWorkspaceById`) — gated by `checkFeatureByPlan('feat:workspaces')`.
`workspaceId` from `req.params.id` only checked for *existence*, never ownership, before a full cascading delete of that workspace's `ChatFlow`, `DocumentStore`, `Evaluation`, `Dataset`, `Credential`, `CustomTemplate`, `ApiKey`, `Assistant`, `Execution`, `ChatMessage`, `UpsertHistory`, and all related rows, then the workspace itself. If confirmed, this allows any user holding `workspace:delete` in their own (possibly free-tier) workspace to permanently destroy any OTHER tenant's entire workspace and all its data, instance-wide.

2. `POST /api/v1/account/invite` (`enterprise/controllers/account.controller.ts:24` → `services/account.service.ts:349`, `saveInviteAccount`) — gated by `checkFeatureByPlan('feat:workspaces')`.
`data.workspace.id` (client-supplied) fetched with no check it belongs to the caller's org; the invite is created against that target workspace with a role scoped only to the target's own org (not the caller's). Effectively lets an attacker self-invite into any workspace instance-wide.

3. `PUT`/`DELETE /api/v1/organizationuser` (`enterprise/controllers/organization-user.controller.ts:103`/`113`) — gated by `checkFeatureByPlan('feat:users')`.
`organizationId`/`userId` taken directly from the request with no check that `organizationId` matches the caller's own org (the `read` handler on the same controller correctly performs this check; `update`/`delete` do not). Enables cross-org member role-change/removal (the delete path can soft-delete + scrub the target `User` row entirely on Enterprise platform).

4. `PUT /api/v1/role` (`enterprise/controllers/role.controller.ts:62` → `services/role.service.ts:119`, `updateRole`) — gated at the mount level: `routes/index.ts:141`, `checkFeatureByPlan('feat:roles')`.
The controller validates that the client-supplied `organizationId` field matches the caller's own org, but never checks that the targeted role (fetched by `id` alone) actually belongs to that org — an attacker can satisfy the assert with their own org id while pointing `id` at a foreign org's role, which `updateRole` then silently modifies anyway (it overwrites `organizationId` back to the role's real org before saving).

5. `POST /api/v1/loginmethod/test` (`enterprise/controllers/login-method.controller.ts:162`, `testConfig`) — blocked by a hardcoded `assertEnterprisePlatform()` (Enterprise-only feature).
Sibling methods `create`/`update` in the same controller correctly call `assertQueryOrganizationMatchesActiveOrg(user, req.body.organizationId)` (confirmed present in current code). `testConfig` never received the same check, and merges the caller-supplied test config with the stored, decrypted `clientSecret` of the TARGET org's real SSO provider before performing a live test call — letting an org admin trigger an SSO handshake using another org's secret. Related prior advisory: GHSA-cwc3-p92j-g7qm / CVE-2026-30823 fixed the identical missing-check on this controller's `create`/`update` — this is that same fix never applied to the third method in the same file.

### Why not live-executed
All five require either a paid Enterprise license (`feat:workspaces`/`feat:users`/`feat:roles` all resolve to `false` on an unlicensed instance's `user.features`) or run only in Enterprise platform mode. We registered a real instance and confirmed via reading `enterprise/rbac/PermissionCheck.ts` and the relevant controllers/services that no ownership check exists anywhere in these five call chains — the same "trace every fetch, confirm no scoping" method that yielded 9 other findings we DID execute to completion in this application (submitted as separate advisories). We ask maintainers to confirm #1–4 in a licensed Enterprise test environment.

### Impact
#1 is the most severe (full cross-tenant data destruction). #2–4 are cross-org privilege escalation / unauthorized access. #5 is unauthorized use of another org's stored secret.

### Suggested fix
For #1–3: add ownership/membership assertions before acting (matching patterns already used elsewhere, e.g. `assertQueryOrganizationMatchesActiveOrg`, `assertWorkspaceIdAccessibleToUser`). For #4: verify `oldRole.organizationId === user.activeOrganizationId` after fetching the role by id, not just that the client-supplied `organizationId` field matches. For #5: add the same `assertQueryOrganizationMatchesActiveOrg` call already present on `create`/`update` in the same controller.

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:N
NingunaPasivaActiva
Confid. (sistema)VC:H
AltoBajoNinguno
Integridad (sistema)VI:H
AltoBajoNinguno
Disponib. (sistema)VA:L
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.3
3.1.3
3.1.4
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
npmflowise
Corregida 3.1.4 -33 d 3.1.4 no afectada
Versiones corregidas3.1.4
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-7x8x-vv46-4579

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