dbcve.org
FlowiseApplication · Flowiseai

CVE-2026-41274

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, the GraphCypherQAChain node forwards user-provided input directly into the Cypher query execution pipeline without proper sanitization. An attacker can inject arbitrary Cypher commands that are executed on the underlying Neo4j database, enabling data exfiltration, modification, or deletion. 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

The GraphCypherQAChain node in Flowise versions prior to 3.1.0 accepts user input and directly concatenates it into Cypher queries executed against the Neo4j database without sanitization or parameterization. This allows an attacker to inject arbitrary Cypher commands, potentially leading to full database compromise including data exfiltration, modification, or deletion.

MitigationUpgrade Flowise to version 3.1.0 or later. If immediate patching is not feasible, review and restrict access to the GraphCypherQAChain node, and implement input validation/parameterization as a temporary measure.

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. Identify your Flowise installation and version
    Locate the Flowise installation (e.g., check package.json, docker image tag, or run 'npm list flowise' if installed via npm). Note the installed version number.
    Affected if The installed version is any version prior to 3.1.0 (e.g., 3.0.x, 2.x, 1.x)
  2. Determine if GraphCypherQAChain node is in use
    Review your Flowise application definitions or chatflows to identify if any flows or configurations include the GraphCypherQAChain node.
    Affected if Any active flow or configuration uses the GraphCypherQAChain node with a Neo4j database connection
  3. Verify the node processes user-supplied input
    Inspect the GraphCypherQAChain node configuration to confirm it accepts user input (e.g., via chat input, API parameters, or external data sources) that could be passed to Cypher queries.
    Affected if User-provided input can reach the GraphCypherQAChain node without intermediate validation or sanitization
  4. Check Neo4j database connection exposure
    Review the database credentials and network access controls configured for the GraphCypherQAChain node to assess the potential blast radius if the injection is exploited.
    Affected if The connected Neo4j database contains sensitive data or has write permissions enabled

You are affected if your Flowise version is below 3.1.0 AND you have any flows using the GraphCypherQAChain node that accept user input.

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. If immediate patching is not feasible, review and restrict access to the GraphCypherQAChain node, and implement input validation/parameterization as a temporary measure.

Recommended fix High confidence

3.1.0

  1. Ensure you have a backup of your current Flowise data and configuration
  2. Stop the running Flowise instance
  3. Update to Flowise version 3.1.0 using your deployment method (Docker image pull, npm update, or package manager used)
  4. Verify the new version is running: check the Flowise startup logs or API version endpoint
  5. Test that the GraphCypherQAChain node functions correctly with the updated version

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

Fix this in Flowise Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41274 — 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-41274 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