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.