CVE Intelligence
Analysis AI-assisted

CVE-2026-41274: Flowise: Cypher Injection in GraphCypherQAChain

CVE-2026-41274 affects Flowise versions before 3.1.0, where the GraphCypherQAChain node passes user input into Cypher query execution without adequate sanitization. The record states that an attacker could run arbitrary Cypher commands against the underlying Neo4j database, creating risk of data exfiltration, modification or deletion. The record lists a CVSS base score of 9.8 from NVD and states that the issue is fixed in 3.1.0.

Published Oct 24, 2026 · Updated Oct 24, 2026 · Ler em português

Overview

Flowise is a drag-and-drop interface for building customized large language model flows. CVE-2026-41274 is a Cypher injection flaw in the GraphCypherQAChain node, classified as CWE-943 in the record. According to the advisory-based data, user input reaches Cypher query execution without proper sanitization.

Impact

  • The record states that injected Cypher commands can be executed against the underlying Neo4j database.
  • The consequences listed in the record include data exfiltration, modification and deletion.
  • The record lists a CVSS base score of 9.8 from NVD and a score of 9.3 from GitHub. These are recorded scores; the record does not describe how they were derived.

Affected products and versions

  • Flowiseai Flowise: versions before 3.1.0.
  • FlowiseAI Flowise-components: versions before 3.1.0.

Exploitation status

  • The record shows this CVE is not listed in the CISA KEV catalogue.
  • No confirmed exploitation in the wild appears in the sources consulted.
  • The SSVC data in the record lists exploitation as 'poc', which points to a proof-of-concept level of maturity. This is not confirmation of active exploitation.

Remediation and mitigation

  • Upgrade Flowise and Flowise-components to 3.1.0 or later, since the record states the fix is in 3.1.0.
  • Until the upgrade is applied, limit who can create or edit flows that use GraphCypherQAChain and restrict access to the Flowise interface to trusted users.
  • Apply least privilege to the Neo4j account used by Flowise so that it can read and write only the data it strictly needs.

Detection guidance

  • Review Neo4j query logs for unexpected write or delete operations originating from the Flowise service account.
  • Review Flowise logs for unusual inputs submitted to chains that run graph queries.

Limitations of the available information

  • The record does not describe the exact vulnerable code path or the input format that triggers the issue.
  • The fixes list in the record is empty. The fixed version 3.1.0 comes from the description and affected version data.
  • The record does not include a CWE name. The EPSS values are recorded as given and reflect an estimated probability, not confirmed exploitation.

Frequently asked questions

Is CVE-2026-41274 known to be exploited in the wild?

The record shows it is not listed in the CISA KEV catalogue, and no confirmed exploitation in the wild appears in the sources consulted.

Which version fixes this issue?

The record states the issue is fixed in 3.1.0, so affected installations should be upgraded to 3.1.0 or a later release.

What data could be affected?

The record says injected Cypher could read, modify or delete data in the underlying Neo4j database.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.