Internal service access via unrestricted HTTP Node
Published Mar 10, 2026 · Updated Mar 10, 2026
SSRF in the HTTP Node in Flowise before 3.0.13 allows remote attackers to access internal services through a publicly exposed chatflow. The node accepts a user-controlled URL and sends server-side HTTP requests without blocking localhost, private address ranges, or cloud metadata endpoints. An attacker must reach a chatflow containing the node; supported HTTP methods permit reading or changing data only where the targeted internal service accepts those requests.
Summary
What happened
SSRF in the HTTP Node in Flowise before 3.0.13 allows remote attackers to access internal services through a publicly exposed chatflow. The node accepts a user-controlled URL and sends server-side HTTP requests without blocking localhost, private address ranges, or cloud metadata endpoints. An attacker must reach a chatflow containing the node; supported HTTP methods permit reading or changing data only where the targeted internal service accepts those requests.
The record
- CVE
- CVE-2026-31829
- Published
- Mar 10, 2026
- Updated
- Mar 10, 2026
- Vendor
- FlowiseAI
- Product
- Flowise
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 10, 2026CVE publishedPublication date reported by the CVE source.
- Mar 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.0.13
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- HTTP Node localhost SSRF proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo