dbcve.org
FlowiseApplication · Flowiseai

CVE-2026-41265

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 specific flaw exists within the run method of the Airtable_Agents class. The issue results from the lack of proper sandboxing when evaluating an LLM generated python script. Using prompt injection techniques, an unauthenticated attacker with the ability to send prompts to a chatflow using the Airtable Agent node may convince an LLM to respond with a malicious python script that executes attacker controlled commands on the flowise server. 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 vulnerability exists in the run method of the Airtable_Agents class where LLM-generated Python scripts are evaluated without proper sandboxing. An unauthenticated attacker with the ability to send prompts to a chatflow using the Airtable Agent node can use prompt injection techniques to cause the LLM to output malicious Python code that executes arbitrary commands on the Flowise server.

MitigationUpgrade Flowise to version 3.1.0 or later to obtain the patch that adds proper sandboxing for evaluated Python scripts in the Airtable_Agents class.

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 Flowise version
    Check the installed Flowise version by inspecting package.json, the Docker image tag, or the /api/v1/version API endpoint if exposed
    Affected if The installed version is below 3.1.0
  2. Locate Airtable Agent node usage
    Search Flowise chatflows for any flow that includes the Airtable Agent node component
    Affected if A chatflow exists that uses the Airtable Agent node
  3. Verify chatflow exposure
    Examine the chatflow settings in Flowise to determine if it is configured as public (no authentication required) or internal
    Affected if The chatflow using Airtable Agent is publicly accessible without authentication
  4. Confirm prompt access
    Verify that the chatflow endpoint accepts unauthenticated HTTP POST requests to the /api/v1/prediction or /api/v1/chatflow/{id} endpoints
    Affected if Unauthenticated users can send prompts to the exposed chatflow

A user is affected if Flowise version is below 3.1.0 AND an Airtable Agent chatflow is publicly accessible without authentication, allowing an unauthenticated attacker to inject malicious Python code via prompts.

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 to obtain the patch that adds proper sandboxing for evaluated Python scripts in the Airtable_Agents class.

Recommended fix High confidence

Flowise version 3.1.0

  1. Identify all Flowise instances currently running version prior to 3.1.0
  2. Review the Flowise release notes for version 3.1.0 to understand the security fix
  3. Plan an upgrade window and backup the current Flowise installation
  4. Upgrade Flowise to version 3.1.0 or later using the appropriate installation method (e.g., npm install, Docker, or binary)
  5. Verify the upgrade was successful by checking the Flowise version
  6. Test the Airtable Agent node functionality to ensure it works correctly after the upgrade
  7. Confirm that prompt injection no longer allows arbitrary command execution

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

Fix this in Flowise Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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