CVE-2026-43995: Flowise Remote Code Execution Vulnerability

MODERATE
Advisory Identifier: GHSA-qqvm-66q4-vf5c
CWE-918
Published
Advisory Summary

CVE-2026-43995 is a MODERATE remote code execution vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting Flowise libraries in the npm ecosystem. The issue involves ssrf protection bypass via direct node-fetch / axios usage (patch enforcement failure). Remediation is available by upgrading affected packages to version 3.1.0.

CVE-2026-43995 at a Glance

CVE Identifier CVE-2026-43995
GHSA Identifier GHSA-qqvm-66q4-vf5c
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product Flowise
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-43995

To remediate this vulnerability, upgrade all affected Flowise dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

flowise fixed: 3.1.0
npm install flowise@3.1.0
flowise-components fixed: 3.1.0
npm install flowise-components@3.1.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls flowise

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-43995, inspect your project dependencies using npm:

npm ls flowise

Analyze the terminal output to locate any version of Flowise in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.1.0), your application is affected.

Note: The npm ls flowise command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In Flowise, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary Flowise introduced SSRF protections through a centralized HTTP security wrapper (`httpSecurity.ts`) that implements deny-list validation and IP pinning logic. However, multiple tool implementations directly import and invoke raw HTTP clients (`node-fetch`, `axios`Instead of using the secured wrapper. Because enforcement is neither mandatory nor centralized, these tools bypass SSRF mitigation entirely, restoring full SSRF capability even after the patch. This issue is distinct from specification trust issues and represents incomplete mitigation of previously addressed SSRF vulnerabilities. ### Details **Intended Security Model:** All outbound HTTP requests should pass through the centralized validation layer implemented in: ``` packages/components/src/httpSecurity.ts ``` This layer performs: - `HTTP_DENY_LIST` enforcement - IP resolution validation - IP pinning - Loopback blocking **Observed Implementation Gap:** Multiple tools bypass this layer and import HTTP libraries directly. Examples include: - `packages/components/nodes/tools/OpenAPIToolkit/OpenAPIToolkit.ts` - `packages/components/nodes/tools/WebScraperTool/WebScraperTool.ts` - `packages/components/nodes/tools/MCP/core.ts` - `packages/components/nodes/tools/Arxiv/core.ts` These files directly execute: ``` importfetchfrom'node-fetch' ``` or invoke `axios` without passing through the centralized validation wrapper. Because there is no global interceptor or enforcement mechanism, outbound requests in these components are executed without SSRF validation. This renders the mitigation introduced in GHSA-2x8m-83vc-6wv4 incomplete. ### Root Cause Security enforcement is not centralized. Outbound request validation depends on voluntary usage of a wrapper function rather than being structurally enforced. Because direct imports of HTTP clients are allowed, the mitigation is easily bypassed. This is an architectural enforcement failure rather than a single implementation bug. ### PoC Even when an administrator configures: ``` HTTP_DENY_LIST=169.254.0.0/16,127.0.0.0/8 ``` The following attack succeeds if a vulnerable tool is enabled: **Chat Prompt:** ``` Use the Web Scraper tool to retrieve: http://169.254.169.254/latest/meta-data/iam/security-credentials/ ``` Execution flow: 1. The LLM triggers `WebScraperTool`. 2. The tool calls raw `fetch()` directly. 3. No `httpSecurity.ts` validation is applied. 4. The request reaches the metadata endpoint. 5. The response is returned to the chat context. This demonstrates that SSRF protection is opt-in rather than enforced. ### Impact **Severity:** Critical (CVSS v3.1: 9.1 – AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) This issue: - Completely bypasses the centralized SSRF mitigation. - Allows access to internal network resources. - Enables the exploitation of cloud metadata and credential theft. - Invalidates the security assumptions of the recent patch. Any deployment enabling affected tools remains vulnerable. ### Recommended Remediation 1. Refactor all tools to use the centralized `secureFetch()` wrapper. 2. Add ESLint `no-restricted-imports` rules to prohibit the direct usage of `node-fetch` or `axios` in tool components. 3. Consider implementing a single internal HTTP client abstraction layer. 4. Apply network-level egress filtering as defense-in-depth.

CVE-2026-43995 Affected Flowise Versions

2 component(s)
Fixed Versions:
3.1.0
Product / Package Ecosystem Affected Versions Fixed Version
flowise
npm
< 3.1.0
3.1.0
flowise-components
npm
< 3.1.0
3.1.0

References

Frequently Asked Questions

What is CVE-2026-43995?
CVE-2026-43995 is a security vulnerability in Flowise involving SSRF Protection Bypass via Direct node-fetch / axios Usage (Patch Enforcement Failure) under CWE-918: Server-Side Request Forgery (SSRF).
Which Flowise versions are affected?
Affected versions include releases prior to 3.1.0 across affected packages: flowise, flowise-components.
What version fixes CVE-2026-43995?
Upgrading to 3.1.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is flowise affected?
Yes, flowise is affected in releases prior to 3.1.0. Upgrade your dependency to 3.1.0 or later.
Is flowise-components affected?
Yes, flowise-components is affected in releases prior to 3.1.0. Upgrade your dependency to 3.1.0 or later.
What CWE is associated with CVE-2026-43995?
CVE-2026-43995 is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check npm dependencies for CVE-2026-43995?
Run the dependency tree command: 'npm ls flowise'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-qqvm-66q4-vf5c",
  "modified" : "2026-05-13T14:04:45Z",
  "published" : "2026-04-16T21:23:03Z",
  "aliases" : [ "CVE-2026-43995" ],
  "summary" : "Flowise: SSRF Protection Bypass via Direct node-fetch / axios Usage (Patch Enforcement Failure)",
  "details" : "### Summary\n\nFlowise introduced SSRF protections through a centralized HTTP security wrapper (`httpSecurity.ts`) that implements deny-list validation and IP pinning logic.\n\nHowever, multiple tool implementations directly import and invoke raw HTTP clients (`node-fetch`, `axios`Instead of using the secured wrapper.\n\nBecause enforcement is neither mandatory nor centralized, these tools bypass SSRF mitigation entirely, restoring full SSRF capability even after the patch.\n\nThis issue is distinct from specification trust issues and represents incomplete mitigation of previously addressed SSRF vulnerabilities.\n\n### Details\n**Intended Security Model:**\n\nAll outbound HTTP requests should pass through the centralized validation layer implemented in:\n\n```\npackages/components/src/httpSecurity.ts\n```\n\nThis layer performs:\n\n- `HTTP_DENY_LIST` enforcement\n- IP resolution validation\n- IP pinning\n- Loopback blocking\n\n**Observed Implementation Gap:**\n\nMultiple tools bypass this layer and import HTTP libraries directly.\n\nExamples include:\n\n- `packages/components/nodes/tools/OpenAPIToolkit/OpenAPIToolkit.ts`\n- `packages/components/nodes/tools/WebScraperTool/WebScraperTool.ts`\n- `packages/components/nodes/tools/MCP/core.ts`\n- `packages/components/nodes/tools/Arxiv/core.ts`\n\nThese files directly execute:\n\n```\nimportfetchfrom'node-fetch'\n```\n\nor invoke `axios` without passing through the centralized validation wrapper.\n\nBecause there is no global interceptor or enforcement mechanism, outbound requests in these components are executed without SSRF validation.\n\nThis renders the mitigation introduced in GHSA-2x8m-83vc-6wv4 incomplete.\n\n### Root Cause\n\nSecurity enforcement is not centralized.\n\nOutbound request validation depends on voluntary usage of a wrapper function rather than being structurally enforced.\n\nBecause direct imports of HTTP clients are allowed, the mitigation is easily bypassed.\n\nThis is an architectural enforcement failure rather than a single implementation bug.\n\n### PoC\nEven when an administrator configures:\n\n```\nHTTP_DENY_LIST=169.254.0.0/16,127.0.0.0/8\n```\n\nThe following attack succeeds if a vulnerable tool is enabled:\n\n**Chat Prompt:**\n\n```\nUse the Web Scraper tool to retrieve:\nhttp://169.254.169.254/latest/meta-data/iam/security-credentials/\n```\n\nExecution flow:\n\n1. The LLM triggers `WebScraperTool`.\n2. The tool calls raw `fetch()` directly.\n3. No `httpSecurity.ts` validation is applied.\n4. The request reaches the metadata endpoint.\n5. The response is returned to the chat context.\n\nThis demonstrates that SSRF protection is opt-in rather than enforced.\n### Impact\n\n**Severity:** Critical (CVSS v3.1: 9.1 – AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N)\n\nThis issue:\n\n- Completely bypasses the centralized SSRF mitigation.\n- Allows access to internal network resources.\n- Enables the exploitation of cloud metadata and credential theft.\n- Invalidates the security assumptions of the recent patch.\n\nAny deployment enabling affected tools remains vulnerable.\n\n### Recommended Remediation\n\n1. Refactor all tools to use the centralized `secureFetch()` wrapper.\n2. Add ESLint `no-restricted-imports` rules to prohibit the direct usage of `node-fetch` or `axios` in tool components.\n3. Consider implementing a single internal HTTP client abstraction layer.\n4. Apply network-level egress filtering as defense-in-depth.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "flowise"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.1.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.0.13"
    }
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "flowise-components"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.1.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.0.13"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-qqvm-66q4-vf5c"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-43995"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/FlowiseAI/Flowise"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-16T21:23:03Z",
    "nvd_published_at" : "2026-05-11T18:16:37Z"
  }
}