CVE-2026-41272 Flowise: SSRF Protection Bypass (TOCTOU & Default Insecure)

High 7.1 Published 23 Apr 2026 Updated 23 Apr 2026

Attackers can bypass SSRF protections in Flowise via DNS rebinding or default insecure settings, potentially accessing internal 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-41272?

CVE-2026-41272 is a high-severity server-side request forgery vulnerability in Flowiseai Flowise, published on 23 Apr 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, the core security wrappers (secureAxiosRequest and secureFetch) intended to prevent Server-Side Request Forgery (SSRF) contain multiple logic flaws. These flaws allow attackers to bypass the allow/deny lists via DNS Rebinding (Time-of-Check Time-of-Use) or by exploiting the default configuration which fails to enforce any deny list. This vulnerability is fixed in 3.1.0.

Weakness: CWE-918

Which versions are affected by CVE-2026-41272?

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

Package	Affected	Fixed in
`flowise` npm	All versions	`3.1.0`
`flowise` npm	All versions	`3.1.0`
`flowise-components` npm	All versions	`3.1.0`
`flowise-components` npm	All versions	`3.1.0`

Products include Flowiseai Flowise.

How do I fix CVE-2026-41272?

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-41272 being exploited?

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

All Flowiseai Flowise vulnerabilities

Sources

Also known as GHSA-2x8m-83vc-6wv4.