CVE-2026-43995: Flowise SSRF protection bypass in multiple tool components

CVE-2026-43995 · Severity: critical · CVSS 9.8 · Published 2026-05-11

Flowise is a low-code platform used to build and deploy custom AI applications and Large Language Model (LLM) workflows. A security flaw in several of its built-in tools allows attackers to bypass internal network protections and force the application to make unauthorized requests to internal servers. This could lead to the theft of sensitive cloud credentials, access to private internal data, or the compromise of other systems within the corporate network.

Technologies: flowise (npm), flowise-components (npm). Vendors: npm.

Quick answers

Is CVE-2026-43995 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-43995 being exploited in the wild.
How severe is CVE-2026-43995?
Critical severity, with a CVSS score of 9.8, published 11 May 2026.
Which products and versions are affected?
flowise (npm) <= 3.0.13, SEMVER:introduced=0,fixed=3.1.0; flowise-components (npm) <= 3.0.13, SEMVER:introduced=0,fixed=3.1.0.
Is there a fix for CVE-2026-43995?
Yes. flowise (npm): upgrade to 3.1.0 or later; flowise-components (npm): upgrade to 3.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-43995 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-43995?
Check whether you run flowise (npm) or flowise-components (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • flowise (npm): upgrade to 3.1.0 or later
    npm install flowise@3.1.0
  • flowise-components (npm): upgrade to 3.1.0 or later
    npm install flowise-components@3.1.0

Technical details

Flowise implements a centralized HTTP security wrapper (httpSecurity.ts) designed to prevent Server-Side Request Forgery (SSRF) by enforcing IP deny-lists and pinning. However, several components—including the OpenAPI Toolkit, Web Scraper, MCP, and Arxiv tools—directly import and invoke raw HTTP clients like 'node-fetch' and 'axios' instead of using the secure wrapper. This architectural failure allows an attacker to bypass SSRF mitigations by providing malicious URLs to these specific tools. An attacker can exploit this to reach internal loopback addresses or cloud provider metadata services (e.g., 169.254.169.254) to exfiltrate IAM credentials or other sensitive environment data. The vulnerability is addressed in version 3.1.0 by refactoring these tools to use the secureFetch wrapper.

Affected products

  • FlowiseAI Flowise < 3.1.0
  • FlowiseAI flowise-components <= 3.0.13

Identifiers

  • CVE-2026-43995
  • GHSA-qqvm-66q4-vf5c

Timeline

  • 2026-04-15: advisory: GitHub Security Advisory published
  • 2026-05-11: disclosed: CVE-2026-43995 published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.