NewApp Monitoring is liveSign up free
AgentbeamBeta
AI agent vulnerability · Flowise

CVE-2026-41277: Flowise: Mass Assignment in DocumentStore Create Endpoint Leads to Cross-Workspace Object Takeover (IDOR)

highCVSS 4.0 7.6 · 3.1 8.8GHSA-3prp-9gf7-4rxx

Flowise 3.0.13 and earlier lets an authenticated user overwrite another workspace's DocumentStore by posting its UUID to the create endpoint. The create call acts as an upsert, so it can modify or reassign the store. Multi-workspace deployments are affected. Upgrade flowise to 3.1.0.

Published Apr 17, 2026 · Updated Apr 24, 2026 · Analysis Oct 29, 2026

What an attacker can do

The DocumentStore create path maps the whole request body onto the entity and calls repository.save(). The entity's primary key is a global uuid, not tied to workspaceId, and the id is accepted from the client. TypeORM's save() updates a row when the id exists and inserts when it does not, so POST /api/v1/document-store with an existing id updates that record. No ownership check runs before the save. The weaknesses are CWE-639, CWE-915 and CWE-284.

An attacker needs a login with low privileges and a valid DocumentStore UUID from another workspace, which they must obtain or enumerate. They can then change the name, description, status, embeddingConfig, vectorStoreConfig and recordManagerConfig. The advisory says the workspaceId might also be overwritten, which would move the store into the attacker's workspace. The advisory hedges that this depends on how the controller handles workspaceId.

DocumentStore objects control embedding providers, vector store settings and record management. Taking one over can change what gets indexed, what retrieval returns, and how AI workflows behave. Single-tenant installs face a much smaller risk.

Who is affected

The flowise npm package at 3.0.13 and earlier, mainly in multi-workspace or multi-tenant deployments where several users share one instance. Check the version:

npm ls -g flowise

The affected endpoint is POST /api/v1/document-store.

flowise

Ecosystem
npm
Affected
<= 3.0.13
Fixed in
3.1.0
Check
npm ls flowise

How to fix it

Upgrade to 3.1.0:

npm install -g [email protected]

The advisory names no workaround. Until you upgrade, limit accounts on shared instances to people who you trust with every workspace's stores, and place a proxy rule or review step on POST /api/v1/document-store requests that include an id in the body.

How to tell if you were hit

Look in access logs for POST /api/v1/document-store requests whose JSON body contains an id field, since a normal create should not send one. Check DocumentStore records for unexpected changes in name, description, status or the embedding, vector store and record manager configs, and for stores that moved to another workspace. The advisory gives no log line.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

Summary

A Mass Assignment vulnerability in the DocumentStore creation endpoint allows authenticated users to control the primary key (id) and internal state fields of DocumentStore entities.

Because the service uses repository.save() with a client-supplied primary key, the POST create endpoint behaves as an implicit UPSERT operation. This enables overwriting existing DocumentStore objects.

In multi-workspace or multi-tenant deployments, this can lead to cross-workspace object takeover and broken object-level authorization (IDOR), allowing an attacker to reassign or modify DocumentStore objects belonging to other workspaces.

Details

The DocumentStore entity defines a globally unique primary key:

@PrimaryGeneratedColumn('uuid')
id: string

The create logic is implemented as:

const documentStore = repo.create(newDocumentStore)
const dbResponse = await repo.save(documentStore)

Here is no DTO allowlist or field filtering before persistence. The entire request body is mapped directly to the entity. TypeORM save() behavior:

  1. If the primary key (id) exists → UPDATE
  2. If not → INSERT

Because id is accepted from the client, the create endpoint effectively functions as an UPSERT endpoint.

This allows an authenticated user to submit:

{
  "id": "<existing_store_id>",
  "name": "modified",
  "description": "modified",
  "status": "SYNC",
  "embeddingConfig": "...",
  "vectorStoreConfig": "...",
  "recordManagerConfig": "..."
}

If a DocumentStore with the supplied id already exists, save() performs an UPDATE rather than creating a new record.

Importantly:

The primary key is globally unique (uuid) It is not composite with workspaceId The create path does not enforce ownership validation before calling save() This introduces a broken object-level authorization risk.

If an attacker can obtain or enumerate a valid DocumentStore UUID belonging to another workspace, they can: Submit a POST create request with that UUID. Trigger an UPDATE on the existing record. Potentially overwrite fields including workspaceId, effectively reassigning the object to their own workspace.

Because the service layer does not verify that the existing record belongs to the caller’s workspace before updating, this may result in cross-workspace object takeover.

Additionally, several service functions retrieve DocumentStore entities by id without consistently scoping by workspaceId, increasing the risk of IDOR if controller-level protections are bypassed or misconfigured.

PoC

  1. Create a normal DocumentStore in Workspace A.
  2. Capture its id from the API response.
  3. From Workspace B (or another authenticated context), submit:
POST /api/v1/document-store
Content-Type: application/json

{
  "id": "<id_from_workspace_A>",
  "name": "hijacked",
  "description": "hijacked"
}

Because the service uses repository.save() with a client-supplied primary key:

  • The existing record is updated.
  • The object may become reassigned depending on how workspaceId is handled at controller level.
  • If workspaceId is overwritten during the create flow, the store is effectively migrated to the attacker’s workspace.
  • This demonstrates object takeover via UPSERT semantics on a create endpoint.

Impact

This vulnerability enables:

  • Mass Assignment on server-managed fields
  • Overwrite of existing objects via implicit UPSERT behavior
  • Broken Object Level Authorization (BOLA)
  • Potential cross-workspace object takeover in multi-tenant deployments
  • In a SaaS or shared-workspace environment, an attacker who can obtain or guess a valid UUID may modify or reassign DocumentStore objects belonging to other tenants.

Because DocumentStore objects control embedding providers, vector store configuration, and record management logic, successful takeover can affect data indexing, retrieval, and AI workflow execution.

This represents a high-risk authorization flaw in multi-tenant environments.

Credited to berkdedekarginoglu.

Questions

Does CVE-2026-41277 need a login?

Yes. The CVSS vector requires low privileges. The attacker needs an account on the instance and a valid DocumentStore UUID from another workspace.

Why does a create endpoint overwrite data?

Flowise passes the client-supplied id to TypeORM's save(), which updates an existing row with that id instead of inserting a new one.

Which version fixes it?

Flowise 3.1.0. Versions up to 3.0.13 are affected.

Does it matter for a single-user install?

Much less. The harm is crossing workspace boundaries, so it matters mostly where multiple workspaces or tenants share an instance.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More Flowise vulnerabilities

All Flowise entries