CVE-2026-130615

Flowise through 3.1.4 SSRF via DNS Rebinding in Playwright and Puppeteer Loaders

Published Nov 17, 2026 CVSS 4.0 · 7.6 High EPSS n/a KEV · Not listed
Description
Flowise through 3.1.4 contains a server-side request forgery vulnerability that allows authenticated users to reach internal services by exploiting unpinned DNS validation in checkDenyList(). Attackers can configure a chatflow with Playwright or Puppeteer loaders using a DNS-rebinding domain so headless Chromium fetches internal or cloud metadata endpoints, returning responses as document content.

Analysis

AI-generated

Technical impact

Flowise version 3.1.4 implements Playwright and Puppeteer loaders that perform DNS validation in the checkDenyList() function. The validation is unpinned, allowing DNS rebinding to redirect the headless Chromium engine to internal or cloud metadata endpoints. An attacker who is authenticated to Flowise can construct a chatflow that directs the loader to a malicious domain, causing the server to fetch internal content and return it as document data. This results in the disclosure of internal information and the ability to reach internal services behind the Flowise installation. The weakness is a classic Server‑Side Request Forgery, classified as CWE‑367.

Affected Systems

The affected product is FlowiseAI's Flowise, with versions up to and including 3.1.4 vulnerable to the described SSRF. Users running any older or equivalent releases that have not applied the fix are potentially exposed.

Risk and Exploitability

The CVSS score of 7.6 indicates a high severity, while the EPSS score is not available. The vulnerability is not currently listed in the CISA KEV catalog. Exploitation requires an authenticated Flowise user who can configure chatflows; the attacker can then use a DNS‑rebinding domain to have headless Chromium reach internal endpoints. Under typical circumstances, once the attacker controls the chatflow, the vulnerability can be leveraged with minimal effort, provided the internal endpoints are reachable from the server. This makes the risk moderate to high for systems that expose internal or metadata services to the Flowise integration.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Flowise to version 3.1.5 or later where DNS validation is corrected.
  • Disable or restrict the use of Playwright and Puppeteer loaders by configuring checkDenyList to allow only whitelisted public domains.
  • Apply network segmentation or firewall rules that block internal service URLs from being accessed by headless Chromium processes.
  • If an upgrade is not immediately possible, block DNS rebinding domains at the DNS or proxy layer to prevent the headless browser from resolving internal hostnames.

Generated by OpenCVE AI on November 17, 2026 at 15:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description Flowise through 3.1.4 contains a server-side request forgery vulnerability that allows authenticated users to reach internal services by exploiting unpinned DNS validation in checkDenyList(). Attackers can configure a chatflow with Playwright or Puppeteer loaders using a DNS-rebinding domain so headless Chromium fetches internal or cloud metadata endpoints, returning responses as document content.
Title Flowise through 3.1.4 SSRF via DNS Rebinding in Playwright and Puppeteer Loaders
First Time appeared Flowiseai
Flowiseai flowise
Weaknesses CWE-367
CPEs cpe:2.3:a:flowiseai:flowise:*:*:*:*:*:*:*:*
Vendors & Products Flowiseai
Flowiseai flowise
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L'}

cvssV4_0

{'score': 7.6, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-367

    Time-of-check Time-of-use (TOCTOU) Race Condition

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 17, 2026, 1:52 PM
Reserved
Nov 17, 2026, 1:45 PM
Status
Deferred
Published
Nov 17, 2026, 2:17 PM
Modified
Nov 17, 2026, 2:17 PM