Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.1amended

Flowise: SSRF Protection Bypass (TOCTOU & Default Insecure)

CVE-2026-41272GHSA-2x8m-83vc-6wv4

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (flowise-components 3.1.0; flowise 3.1.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.1 · CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
EPSS
  • CVE-2026-41272: 0.26% estimated exploitation activity in the next 30 days; percentile 17.56 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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. Details The flaws exist in packages/components/src/httpSecurity.ts. Default Insecure: If process.env.HTTPDENYLIST is undefined, checkDenyList returns immediately, allowing all requests (including localhost). DNS Rebinding (TOCTOU): The function performs a DNS lookup (dns.lookup) to validate the IP, and then the HTTP client performs a new lookup to connect. An attacker can serve a valid IP first, then switch to an internal IP (e.g., 127.0.0.1) for the second lookup. PoC Ensure HTTPDENYLIST is unset (default behavior). Use any node utilizing secureFetch to access http://127.0.0.1. Result: Request succeeds. Scenario 2: DNS Rebinding Attacker controls…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-2x8m-83vc-6wv4

  2. Revision 1 · created ·

    Published from osv record GHSA-2x8m-83vc-6wv4

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41272

Advisory: Flowise: SSRF Protection Bypass (TOCTOU & Default Insecure)
IDs: CVE-2026-41272, GHSA-2x8m-83vc-6wv4
Record: https://patchnext.com/advisories/cve-2026-41272 (revision 2, source checked 26 Oct 2026, 12:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: flowise-components 3.1.0; flowise 3.1.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm flowise-components: affected <= 3.0.13; fixed in 3.1.0
- npm flowise: affected <= 3.0.13; fixed in 3.1.0

## Suggested inspection (read-only)
- `npm ls flowise-components --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls flowise --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on flowise-components, flowise.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-2x8m-83vc-6wv4 (OSV record GHSA-2x8m-83vc-6wv4 lists affected ranges: npm flowise >=0 =0 <3.1.0 (fixed))
- Verified: https://github.com/advisories/GHSA-2x8m-83vc-6wv4 (GitHub-reviewed advisory GHSA-2x8m-83vc-6wv4 lists affected ranges: npm flowise >=0 =0 <=3.0.13)

Commands are suggestions: review each one before running it.

Loading voting…