dbcve.org
FlowiseApplication · Flowiseai

CVE-2026-41276

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-23
Fix available
A fix is available. Upgrade to 3.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, this vulnerability allows remote attackers to bypass authentication on affected installations of FlowiseAI Flowise. Authentication is not required to exploit this vulnerability. The specific flaw exists within the resetPassword method of the AccountService class. There is no check performed to ensure that a password reset token has actually been generated for a user account. By default the value of the reset token stored in a users account is null, or an empty string if they've reset their password before. An attacker with knowledge of the user's email address can submit a request to the "/api/v1/account/reset-password" endpoint containing a null or empty string reset token value and reset that user's password to a value of their choosing. This vulnerability is fixed in 3.1.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

FlowiseAI Flowise prior to version 3.1.0 contains an authentication bypass in the password reset functionality. The resetPassword method in AccountService does not validate whether a password reset token was actually generated for the target user account. Since the token field defaults to null or empty string, an attacker with knowledge of a user's email can reset that user's password by sending a crafted request to /api/v1/account/reset-password with a null/empty token value.

MitigationUpgrade Flowise to version 3.1.0 or later, which implements proper validation of password reset tokens before allowing password changes. Until patched, disable or restrict access to the password reset endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FlowiseApplication
Affected:< 3.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Flowise version
    Locate the Flowise installation and check the version field in package.json or package-lock.json, or run 'npm list flowise' if installed as a dependency. Compare the version number to the 3.1.0 threshold.
    Affected if The installed version is any release prior to 3.1.0 (e.g., 3.0.0, 2.x, 1.x).
  2. Confirm password reset endpoint is accessible
    Verify that the /api/v1/account/reset-password endpoint is reachable from your network. This can be confirmed by reviewing reverse proxy configurations, firewall rules, or by attempting a GET request to the endpoint (which should return a 405 Method Not Allowed if the route exists).
    Affected if The endpoint is exposed to untrusted networks or the internet without additional authentication layers.
  3. Check authentication configuration
    Review the Flowise configuration files or environment variables to determine if external authentication (such as OAuth, LDAP, or SSO) is configured as the primary authentication method rather than Flowise's built-in account system.
    Affected if Flowise's native username/password authentication is in use without external auth, and the version is below 3.1.0.

A user is affected if Flowise version is below 3.1.0 AND the built-in account system is active, allowing a remote attacker to reset any user's password by submitting a crafted request with an empty token to the reset-password endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.1.0 or later
Fixed in 3.1.0
Interim mitigation

Upgrade Flowise to version 3.1.0 or later, which implements proper validation of password reset tokens before allowing password changes. Until patched, disable or restrict access to the password reset endpoint.

Recommended fix High confidence

Flowise 3.1.0 or later

  1. Check current Flowise version by accessing the admin interface or checking the running container/process
  2. Backup any existing Flowise data, configurations, and databases before upgrading
  3. Upgrade Flowise to version 3.1.0 or later. If using Docker, pull the latest image: docker pull flowiseai/flowise:latest or specify version 3.1.0
  4. If using npm/package installation, run: npm install -g [email protected] or npm install [email protected]
  5. Restart the Flowise service to apply the update
  6. Verify the upgrade was successful by checking the version in the admin interface or API
  7. Confirm the /api/v1/account/reset-password endpoint now properly validates reset tokens before allowing password changes
Caveat Review Flowise 3.1.0 release notes for any configuration or feature changes that may affect your deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Flowise Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41276 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41276 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data