Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

Flowise has Authentication Bypass Using Unprotected Registration Endpoint (/register)

CVE-2025-71327GHSA-v5w9-prxf-w882

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm flowise

    Affected
    >= 3.0.1, <= 3.0.1
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · 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 · score source
EPSS
  • CVE-2025-71327: 0.68% estimated exploitation activity in the next 30 days; percentile 52.25 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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. After successful deployment the instance setup organization page allows us to register the first account in the system. Creating the first user research@evasec.io Login to the account The background request that created the first user to /api/v1/account/register Response We have found that it is possible to reuse the registration request multiple times without any restrictions…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-v5w9-prxf-w882

  2. Revision 2 · amended ·

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

  3. Revision 1 · created ·

    Published from osv record GHSA-v5w9-prxf-w882

Agent brief

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

# Patch Next advisory brief: CVE-2025-71327

Advisory: Flowise has Authentication Bypass Using Unprotected Registration Endpoint (/register)
IDs: CVE-2025-71327, GHSA-v5w9-prxf-w882
Record: https://patchnext.com/advisories/cve-2025-71327 (revision 3, source checked 26 Oct 2026, 12:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm flowise: affected >= 3.0.1, <= 3.0.1

## 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
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## 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-v5w9-prxf-w882 (OSV record GHSA-v5w9-prxf-w882 lists affected ranges: npm flowise >=3.0.1 <=3.0.1)
- Verified: https://github.com/advisories/GHSA-v5w9-prxf-w882 (GitHub-reviewed advisory GHSA-v5w9-prxf-w882 lists affected ranges: npm flowise >=3.0.1 <=3.0.1)

Commands are suggestions: review each one before running it.

Loading voting…