CVE-2026-43995 Flowise: SSRF Protection Bypass via Direct node-fetch / axios Usage (Patch Enforcement Failure)

Medium 5.3 Published Updated

Attackers can bypass SSRF protections in Flowise by exploiting tools that use raw HTTP clients, potentially accessing internal network resources.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-43995?

CVE-2026-43995 is a medium-severity server-side request forgery vulnerability in Flowiseai Flowise, published on 11 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, multiple tool implementations directly import and invoke raw HTTP clients (node-fetch, axios) instead of using the secured wrapper. These tools include (1) OpenAPIToolkit/OpenAPIToolkit.ts, (2) WebScraperTool/WebScraperTool.ts, (3) MCP/core.ts, and (4) Arxiv/core.ts. This vulnerability is fixed in 3.1.0.

Weakness: CWE-918

Which versions are affected by CVE-2026-43995?

4 open source packages ship an affected version, including flowise and flowise-components. It affects 1 product.

PackageAffectedFixed in
flowise npmAll versions3.1.0
flowise npmAll versions3.1.0
flowise-components npmAll versions3.1.0
flowise-components npmAll versions3.1.0

Products include Flowiseai Flowise.

How do I fix CVE-2026-43995?

Upgrade flowise to 3.1.0 or later.

Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.

Is CVE-2026-43995 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-43995 exists.

All Flowiseai Flowise vulnerabilities

Sources

Also known as GHSA-qqvm-66q4-vf5c.

Is CVE-2026-43995 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free