GHSA-v5w9-prxf-w882: Flowise Authentication Bypass Vulnerability

HIGH
Share
CWE-287
Published
Advisory Summary

GHSA-v5w9-prxf-w882 is a HIGH authentication bypass vulnerability (CWE-287: Improper Authentication) affecting Flowise libraries in the npm ecosystem. The issue involves flowise has authentication bypass using unprotected registration endpoint (/register). Remediation is available in the latest vendor maintenance releases.

GHSA-v5w9-prxf-w882 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-v5w9-prxf-w882
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-287: Improper Authentication
Affected Product Flowise
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-v5w9-prxf-w882

To remediate this vulnerability, upgrade all affected Flowise dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

flowise fixed: Latest secure release 
npm install flowise@Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls flowise

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-v5w9-prxf-w882, inspect your project dependencies using npm:

npm ls flowise

Analyze the terminal output to locate any version of Flowise in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The npm ls flowise command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-287: Improper Authentication, where when an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. In Flowise, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary An unauthenticated attacker can exploit the unprotected registration endpoint (/register) to create a new user and bypass authentication. ### Details Critical vulnerability in Flowise 3.0.1 on-premise deployment allows unauthenticated attackers to exploit the /api/v1/account/register endpoint to add a new user and log in using it, enabling authentication bypass. Meaning that the register functionality is by default open, allowing attackers to create an account and use the api without any restrictions or credentials. ### PoC A Flowise 3.0.1 instance was deployed via Docker for the purpose of this demonstration. ![1 Docker](https://github.com/user-attachments/assets/fb0b8627-63e3-4523-881f-a0ff6352b678) After successful deployment the instance setup organization page allows us to register the first account in the system. ![1 newly deployed instance](https://github.com/user-attachments/assets/39d56738-eb97-469e-b96e-61cd7cec64a8) Creating the first user [research@evasec.io](mailto:research@evasec.io) ![2 configuring account](https://github.com/user-attachments/assets/5fb94b35-c180-4d77-b209-dcff7043c457) Login to the account ![2 Login](https://github.com/user-attachments/assets/557e8268-099a-4519-bf86-b96a7c5f19ff) The background request that created the first user to /api/v1/account/register ![3 request](https://github.com/user-attachments/assets/b74b876d-b784-4142-9d46-10e90ff1b780) Response ![3 1 response](https://github.com/user-attachments/assets/db769da7-d241-4f0b-a99f-821fa5fdcf05) We have found that it is possible to reuse the registration request multiple times without any restrictions to create an account and authenticate to the system using it. Crafting a new request { "user": { "name": "Malicious", "email": "attacker@attack.io", "type": "pro", "credential": "Password123!" } } ![4 attacker new register](https://github.com/user-attachments/assets/ee34b9f9-7e03-4198-affa-cf2dd2f84666) Response with 201 code “Created” ![4 1 created](https://github.com/user-attachments/assets/e2a49518-1566-4fe0-9cc5-2a496265974a) Login using newly created user (attacker) ![5 Login using attacker](https://github.com/user-attachments/assets/b6ef7eb2-d388-469d-92d7-0ca50cdd9873) Success login ![6 Susccess auth bypass](https://github.com/user-attachments/assets/044376d8-f9c5-4de7-a53c-05dd2c66de83) An unauthorized user can exploit this vulnerability to register an account and gain access to the Flowise API with authenticated privileges, effectively bypassing authentication. ### Impact This is an authentication bypass vulnerability caused by an unprotected registration endpoint (/register). Users of Flowise 3.0.1(latest) on-premise deployments are impacted. An unauthorized attacker can exploit this vulnerability to register an account after the organization set has been completed, and gain access to the Flowise API with authenticated privileges, effectively bypassing authentication.

GHSA-v5w9-prxf-w882 Affected Flowise Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
flowise
npm/flowise
npm
3.0.1
All 1 versions
3.0.1
None specified

References

GitHub Advisory / Wiki ADVISORY
https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-v5w9-prxf-w882
Flowise Source Repository REPOSITORY
https://github.com/FlowiseAI/Flowise

Frequently Asked Questions

What is GHSA-v5w9-prxf-w882?
GHSA-v5w9-prxf-w882 is a security vulnerability in Flowise involving Flowise has Authentication Bypass Using Unprotected Registration Endpoint (/register) under CWE-287: Improper Authentication.
Which Flowise versions are affected?
Affected versions include releases prior to current release patches across affected packages: flowise.
What version fixes GHSA-v5w9-prxf-w882?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is flowise affected?
Yes, flowise is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What CWE is associated with GHSA-v5w9-prxf-w882?
GHSA-v5w9-prxf-w882 is classified under CWE-287: Improper Authentication (When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.).
How can I check npm dependencies for GHSA-v5w9-prxf-w882?
Run the dependency tree command: 'npm ls flowise'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-v5w9-prxf-w882",
  "modified" : "2025-11-17T19:06:09Z",
  "published" : "2025-11-17T19:06:09Z",
  "aliases" : [ ],
  "summary" : "Flowise has Authentication Bypass Using Unprotected Registration Endpoint (/register)",
  "details" : "### Summary\nAn unauthenticated attacker can exploit the unprotected registration endpoint (/register) to create a new user and bypass authentication.\n### Details\nCritical vulnerability in Flowise 3.0.1 on-premise deployment allows unauthenticated attackers to exploit the /api/v1/account/register endpoint to add a new user and log in using it, enabling authentication bypass.\n\nMeaning that the register functionality is by default open, allowing attackers to create an account and use the api without any restrictions or credentials.\n\n### PoC\nA Flowise 3.0.1 instance was deployed via Docker for the purpose of this demonstration.\n![1 Docker](https://github.com/user-attachments/assets/fb0b8627-63e3-4523-881f-a0ff6352b678)\n\nAfter successful deployment the instance setup organization page allows us to register the first account in the system.\n![1 newly deployed instance](https://github.com/user-attachments/assets/39d56738-eb97-469e-b96e-61cd7cec64a8)\n\nCreating the first user [research@evasec.io](mailto:research@evasec.io)\n![2 configuring account](https://github.com/user-attachments/assets/5fb94b35-c180-4d77-b209-dcff7043c457)\n\nLogin to the account\n![2 Login](https://github.com/user-attachments/assets/557e8268-099a-4519-bf86-b96a7c5f19ff)\n\nThe background request that created the first user to /api/v1/account/register \n![3 request](https://github.com/user-attachments/assets/b74b876d-b784-4142-9d46-10e90ff1b780)\n\nResponse\n![3 1 response](https://github.com/user-attachments/assets/db769da7-d241-4f0b-a99f-821fa5fdcf05)\n\nWe have found that it is possible to reuse the registration request multiple times without any restrictions to create an account and authenticate to the system using it.\n\nCrafting a new request \n{\n    \"user\": {\n        \"name\": \"Malicious\",\n        \"email\": \"attacker@attack.io\", \n        \"type\": \"pro\",\n        \"credential\": \"Password123!\"\n    }\n}\n![4 attacker new register](https://github.com/user-attachments/assets/ee34b9f9-7e03-4198-affa-cf2dd2f84666)\n\nResponse with 201 code “Created”\n![4 1 created](https://github.com/user-attachments/assets/e2a49518-1566-4fe0-9cc5-2a496265974a)\n\nLogin using newly created user (attacker)\n![5 Login using attacker](https://github.com/user-attachments/assets/b6ef7eb2-d388-469d-92d7-0ca50cdd9873)\n\nSuccess login\n![6 Susccess auth bypass](https://github.com/user-attachments/assets/044376d8-f9c5-4de7-a53c-05dd2c66de83)\n\n\nAn unauthorized user can exploit this vulnerability to register an account and gain access to the Flowise API with authenticated privileges, effectively bypassing authentication. \n### Impact\n\nThis is an authentication bypass vulnerability caused by an unprotected registration endpoint (/register).\n\nUsers of Flowise 3.0.1(latest) on-premise deployments are impacted. An unauthorized attacker can exploit this vulnerability to register an account after the organization set has been completed, and gain access to the Flowise API with authenticated privileges, effectively bypassing authentication.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "flowise"
    },
    "versions" : [ "3.0.1" ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-v5w9-prxf-w882"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/FlowiseAI/Flowise"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-287" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-11-17T19:06:09Z",
    "nvd_published_at" : null
  }
}