CVE-2026-31829
Server-Side Request Forgery in Flowise HTTP Node Allows Internal Access
Publication date: 2026-03-10
Last updated on: 2026-03-11
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| flowiseai | flowise | to 3.0.13 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Flowise versions prior to 3.0.13, where an HTTP Node in AgentFlow and Chatflow allows server-side HTTP requests using URLs controlled by users. There are no restrictions on the target hosts, meaning users can make the server send requests to internal or private network addresses, including localhost and cloud metadata endpoints.
This behavior enables a Server-Side Request Forgery (SSRF) attack, where an attacker can trick the Flowise server into accessing internal network resources that are normally inaccessible from the public internet.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to access internal network resources through the Flowise server by exploiting the SSRF flaw. This can lead to unauthorized access to sensitive internal services, data leakage, or further attacks within the internal network.
Because the attacker can reach private IP ranges, localhost, or cloud metadata endpoints, they might retrieve sensitive information or manipulate internal systems that are not exposed to the public internet.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade Flowise to version 3.0.13 or later, where the issue has been fixed.