Is CVE-2026-41277 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-41277 being exploited in the wild.

How severe is CVE-2026-41277?

High severity, with a CVSS score of 8.8, published 23 April 2026.

Which products and versions are affected?

flowise (npm) <= 3.0.13, SEMVER:introduced=0,fixed=3.1.0.

Is there a fix for CVE-2026-41277?

Yes. flowise (npm): upgrade to 3.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-41277 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-41277?

Check whether you run FlowiseAI Flowise or flowise (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

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

Q: Which products and versions are affected?

flowise (npm) <= 3.0.13, SEMVER:introduced=0,fixed=3.1.0.

Q: Is there a fix for CVE-2026-41277?

Yes. flowise (npm): upgrade to 3.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-41277 attacked?

It is attacked over the network, in a web application.

Q: Am I affected by CVE-2026-41277?

Check whether you run FlowiseAI Flowise or flowise (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-41277 · Severity: high · CVSS 8.8 · Published 2026-04-23

Flowise is a platform for building AI agents visually using document stores to manage embeddings and vector data. An authenticated attacker can exploit a flaw in the DocumentStore creation endpoint to overwrite or steal DocumentStore objects from other workspaces by submitting a request with an existing object's ID. This could allow an attacker to modify AI workflow configurations, redirect data indexing to their own infrastructure, or gain unauthorized access to embedding and vector storage settings belonging to other tenants in a shared environment.

Technologies: FlowiseAI Flowise, flowise (npm). Vendors: FlowiseAI, npm.

Quick answers

Is CVE-2026-41277 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-41277 being exploited in the wild.
How severe is CVE-2026-41277?: High severity, with a CVSS score of 8.8, published 23 April 2026.
Which products and versions are affected?: flowise (npm) <= 3.0.13, SEMVER:introduced=0,fixed=3.1.0.
Is there a fix for CVE-2026-41277?: Yes. flowise (npm): upgrade to 3.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41277 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-41277?: Check whether you run FlowiseAI Flowise or flowise (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

flowise (npm): upgrade to 3.1.0 or later
```
npm install flowise@3.1.0
```

Technical details

The vulnerability is a mass assignment and broken object-level authorization (BOLA) flaw in the DocumentStore entity creation logic. The root cause is that Flowise accepts a client-supplied primary key (id) without validation and passes the entire request body directly to the ORM's save() operation. TypeORM's save() method performs an UPDATE if the primary key already exists, converting the create endpoint into an implicit UPSERT operation. An authenticated attacker can obtain a valid DocumentStore UUID from another workspace and submit a POST /api/v1/document-store request with that ID, causing the existing record to be overwritten. Since the primary key is globally unique (not scoped to workspace) and the service layer does not validate ownership before updating, an attacker can effectively reassign a DocumentStore to their workspace. The vulnerability requires authentication and network access, but no special privileges. Flowise fixed this in version 3.1.0; all versions ≤ 3.0.13 are affected.

Affected products

FlowiseAI flowise < 3.1.0

Identifiers

CVE-2026-41277
GHSA-3prp-9gf7-4rxx

Timeline

2026-04-17: disclosed: Advisory GHSA-3prp-9gf7-4rxx published
2026-04-17: patched: Fixed in version 3.1.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.