FlowiseAI: Evaluator create+update mass-assignment allows cross-workspace evaluator takeover

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.7 · 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 · score source

EPSS

• CVE-2026-46480: 0.34% estimated exploitation activity in the next 30 days; percentile 26.94 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Type: Mass assignment via Object.assign(entity, body) - client-controlled workspaceId (and on create, id) overwritten on the Evaluator entity - cross-workspace data takeover and IDOR. File: packages/server/src/Interface.Evaluation.ts Root cause: The Evaluator controller/service constructs a new Evaluator() and copies the request body into it via Object.assign(...) without an explicit field allowlist. The request body therefore can include workspaceId, id, createdDate, updatedDate. The server only rebinds some of these after the assign (e.g. on create, it overwrites workspaceId but not id; on update, it overwrites id but not workspaceId). The remaining client-controlled values land directly on the persisted row, breaking workspace isolation. Same root pattern as the evaluator entity's sibling controllers and as DocumentStore before it was patched in commit 840d2ae. Affected Code File: packages/server/src/Interface.Evaluation.ts Why it's wrong: Object.assign(target, source)…

Published by the source

14 May 2026, 16:19 UTC

Last modified by the source

9 Jun 2026, 18:45 UTC

Source last checked

26 Oct 2026, 12:53 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-wxrr-jp8m-qq7f

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-wxrr-jp8m-qq7f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-46480

Advisory: FlowiseAI: Evaluator create+update mass-assignment allows cross-workspace evaluator takeover
IDs: CVE-2026-46480, GHSA-wxrr-jp8m-qq7f
Record: https://patchnext.com/advisories/cve-2026-46480 (revision 3, source checked 26 Oct 2026, 12:53 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: flowise 3.1.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm flowise: affected <= 3.1.1; fixed in 3.1.2

## Suggested inspection (read-only)
- `npm ls flowise --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on flowise.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-wxrr-jp8m-qq7f (OSV record GHSA-wxrr-jp8m-qq7f lists affected ranges: npm flowise >=0 <3.1.2 (fixed))
- Verified: https://github.com/advisories/GHSA-wxrr-jp8m-qq7f (GitHub-reviewed advisory GHSA-wxrr-jp8m-qq7f lists affected ranges: npm flowise >=0 <=3.1.1)

Commands are suggestions: review each one before running it.