GHSA-hp26-q66v-q2w7 — flowise
GHSA-hp26-q66v-q2w7 is a CWE-284 vulnerability in flowise. A fix is available for flowise — see the affected versions and patch details below.
FlowiseAI has Mass Assignment in Assistant Update Endpoint that Allows Cross-Workspace Resource Reassignment
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-hp26-q66v-q2w7.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
flowisenpmDescription
Summary
A Mass Assignment vulnerability exists in the assistant update endpoint of FlowiseAI.
The endpoint allows authenticated users to modify server-controlled properties such as workspaceId, createdDate, and updatedDate when updating an assistant resource.
Due to missing server-side validation and authorization checks, an attacker can manipulate the workspaceId field and reassign assistants to arbitrary workspaces. This breaks tenant isolation in multi-workspace environments.
Details
The endpoint responsible for updating assistants:
PUT /api/v1/assistants/{assistantId}
accepts a JSON request body containing assistant metadata.
However, the server does not restrict which properties may be modified by the client. As a result, user-controlled request bodies can include additional fields that should normally be controlled only by the backend.
Server-controlled fields that can be manipulated include:
- workspaceId
- createdDate
- updatedDate
These fields appear to be directly mapped to the underlying database entity without strict DTO whitelisting or authorization checks.
For example, the following request body was accepted:
{
"details": "",
"credential": "11ca7fef-c9b1-4c87-aa54-e547aed8a249",
"iconSrc": null,
"type": "CUSTOM",
"createdDate": "2026-03-06T17:31:04.000Z",
"updatedDate": "2026-03-06T17:31:55.000Z",
"workspaceId": "11111111-2222-3333-4444-555555555555"
}
This indicates that internal, server-controlled properties can be modified by an authenticated user.
PoC
- Authenticate to the Flowise interface.
- Capture the request used to update an assistant:
PUT /api/v1/assistants/<ASSISTANT_ID>
Content-Type: application/json
Modify the request body by injecting server-controlled fields:
{
"details": "",
"credential": "11ca7fef-c9b1-4c87-aa54-e547aed8a249",
"iconSrc": null,
"type": "CUSTOM",
"createdDate": "2026-03-06T17:31:04.000Z",
"updatedDate": "2026-03-06T17:31:55.000Z",
"workspaceId": "11111111-2222-3333-4444-555555555555"
}
3.Send the request.
Observe that the response accepts and persists the attacker-controlled workspaceId and metadata fields.
Impact
This vulnerability allows authenticated users to manipulate internal attributes of assistant resources.
Confirmed impacts include:
- Cross-workspace reassignment of assistants (workspaceId)
- Unauthorized modification of metadata (createdDate, updatedDate)
In multi-tenant deployments, this may allow an attacker to move assistants between workspaces without authorization, breaking tenant isolation boundaries.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | flowise | all versions | 3.1.2npm install flowise@3.1.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flowise, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update flowise to 3.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hp26-q66v-q2w7 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hp26-q66v-q2w7 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-hp26-q66v-q2w7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-hp26-q66v-q2w7 in your dependencies?
O3 Security finds GHSA-hp26-q66v-q2w7 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.