CVE-2026-130615: Flowise: SSRF via DNS rebinding in web loaders
HIGHFlowise through 3.1.4 has a server-side request forgery flaw: the checkDenyList() DNS validation is not pinned, so an authenticated user can use a DNS-rebinding domain in a Playwright or Puppeteer loader to make headless Chromium fetch internal services or cloud metadata endpoints and return the responses as document content. Real-world risk is moderate: it needs a low-privilege account and a DNS-rebinding setup (high complexity), and no public exploit, Nuclei template, KEV listing or EPSS score is available yet. The impact is still serious because the metadata endpoints it reaches can hand out cloud IAM credentials, which would give an attacker a path from the AI agent platform into the wider cloud environment. The vendor references a sunset page, so confirm whether a fixed release exists or whether Flowise is end-of-life before relying on patching. Until then, restrict who can create chatflows, enforce IMDSv2 with hop limit 1, and block egress from Flowise hosts to internal ranges and 169.254.169.254.
What is the risk?
High (CVSS 7.1). Network-reachable, low privileges required, no user interaction. Attack complexity is high because the attacker must win a DNS-rebinding race against validation. Confidentiality and integrity impact are rated high, availability low. There is no known public exploit, Nuclei template or KEV listing, and EPSS is unavailable, so near-term mass exploitation is less likely, but exposure rises sharply for multi-tenant or internet-facing Flowise instances running on cloud VMs with reachable metadata services. The vendor sunset notice raises the chance that a patch is slow or never arrives.
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| Flowise | npm | — | No patch |
Do you use Flowise? You're affected.
How severe is it?
What is the attack surface?
What should I do?
1 step1) Check the vendor advisory and the Flowise sunset page for a fixed version or migration guidance; upgrade past 3.1.4 if a fix exists, or plan migration if the product is end-of-life. 2) Limit chatflow creation and loader use to trusted users, and review existing chatflows for Playwright or Puppeteer loader nodes. 3) Disable or remove the Playwright and Puppeteer loader nodes if not needed. 4) Enforce egress filtering from the Flowise host and container to RFC1918 ranges, link-local 169.254.169.254 and internal management networks. 5) Require IMDSv2 with hop limit 1 (or the equivalent on other clouds) and use least-privilege instance roles. 6) Detect: monitor DNS logs for short-TTL or rebinding-style domains resolving to internal IPs, and watch for outbound requests from Flowise to metadata or internal addresses and for unusual chatflow edits.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-130615?
Flowise through 3.1.4 has a server-side request forgery flaw: the checkDenyList() DNS validation is not pinned, so an authenticated user can use a DNS-rebinding domain in a Playwright or Puppeteer loader to make headless Chromium fetch internal services or cloud metadata endpoints and return the responses as document content. Real-world risk is moderate: it needs a low-privilege account and a DNS-rebinding setup (high complexity), and no public exploit, Nuclei template, KEV listing or EPSS score is available yet. The impact is still serious because the metadata endpoints it reaches can hand out cloud IAM credentials, which would give an attacker a path from the AI agent platform into the wider cloud environment. The vendor references a sunset page, so confirm whether a fixed release exists or whether Flowise is end-of-life before relying on patching. Until then, restrict who can create chatflows, enforce IMDSv2 with hop limit 1, and block egress from Flowise hosts to internal ranges and 169.254.169.254.
Is CVE-2026-130615 actively exploited?
No confirmed active exploitation of CVE-2026-130615 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-130615?
1) Check the vendor advisory and the Flowise sunset page for a fixed version or migration guidance; upgrade past 3.1.4 if a fix exists, or plan migration if the product is end-of-life. 2) Limit chatflow creation and loader use to trusted users, and review existing chatflows for Playwright or Puppeteer loader nodes. 3) Disable or remove the Playwright and Puppeteer loader nodes if not needed. 4) Enforce egress filtering from the Flowise host and container to RFC1918 ranges, link-local 169.254.169.254 and internal management networks. 5) Require IMDSv2 with hop limit 1 (or the equivalent on other clouds) and use least-privilege instance roles. 6) Detect: monitor DNS logs for short-TTL or rebinding-style domains resolving to internal IPs, and watch for outbound requests from Flowise to metadata or internal addresses and for unusual chatflow edits.
What systems are affected by CVE-2026-130615?
This vulnerability affects the following AI/ML architecture patterns: agent frameworks, RAG pipelines, low-code LLM workflow builders, web-scraping document loaders.
What is the CVSS score for CVE-2026-130615?
CVE-2026-130615 has a CVSS v3.1 base score of 7.1 (HIGH).
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0049Exploit Public-Facing ApplicationAML.T0053AI Agent Tool InvocationAML.T0055Unsecured CredentialsAML.T0075Cloud Service DiscoveryCompliance Controls Affected
What are the technical details?
Original Advisory
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.
Exploitation Scenario
An attacker with a low-privilege Flowise account creates a chatflow containing a Puppeteer web loader pointed at an attacker-controlled domain with a DNS-rebinding setup. The domain first resolves to a public IP so checkDenyList() passes, then re-resolves to 169.254.169.254 when headless Chromium makes the actual request. The loader fetches the cloud metadata service and returns the IAM role credentials as document content in the chat response. The attacker then uses those credentials against the victim's cloud account to reach storage, secrets or model endpoints.
Weaknesses (CWE)
CWE-367Time-of-check Time-of-use (TOCTOU) Race ConditionPrimaryCWE-367Time-of-check Time-of-use (TOCTOU) Race ConditionCWE-367 — Time-of-check Time-of-use (TOCTOU) Race Condition: The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.
- [Implementation] The most basic advice for TOCTOU vulnerabilities is to not perform a check before the use. This does not resolve the underlying issue of the execution of a function on a resource whose state and identity cannot be assured, but it does help to limit the false sense of security given by the check.
- [Implementation] When the file being altered is owned by the current user and group, set the effective gid and uid to that of the current user and group when executing this statement.
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:LReferences
- flowiseai.com/sunset
- github.com/FlowiseAI/Flowise/blob/a65f81bb43ef66d3ce734bf0dff4223ae8041c95/packages/components/nodes/documentloaders/Playwright/Playwright.ts
- github.com/FlowiseAI/Flowise/blob/a65f81bb43ef66d3ce734bf0dff4223ae8041c95/packages/components/nodes/documentloaders/Puppeteer/Puppeteer.ts
- github.com/FlowiseAI/Flowise/blob/a65f81bb43ef66d3ce734bf0dff4223ae8041c95/packages/components/src/httpSecurity.ts
- github.com/FlowiseAI/Flowise/blob/main/SECURITY.md
- vulncheck.com/advisories/flowise-through-3.1.4-ssrf-via-dns-rebinding-in-playwright-and-puppeteer-loaders
Timeline
Related Vulnerabilities
CVE-2025-7133810.0Flowise: unauthenticated file write enables RCE
Same package: flowiseCVE-2025-5952810.0Flowise: Unauthenticated RCE via MCP config injection
Same package: flowiseCVE-2026-464429.9Flowise: sandbox escape enables authenticated RCE
Same package: flowiseCVE-2025-619139.9Flowise: path traversal in file tools leads to RCE
Same package: flowiseCVE-2026-409339.9Flowise: RCE via MCP stdio command injection
Same package: flowise