CVE-2026-31829: Flowise affected by Server-Side Request Forgery (SSRF) in HTTP Node Leading to Internal Network Access
Noroxi assessment
Priority: Monitor (action score 36/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.6% (FIRST EPSS); higher than 86.1% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: FlowiseAI Flowise 3.0.13.
Low priority for now. Upgrade to FlowiseAI Flowise 3.0.13 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.0.13, Flowise exposes an HTTP Node in AgentFlow and Chatflow that performs server-side HTTP requests using user-controlled URLs. By default, there are no restrictions on target hosts, including private/internal IP ranges (RFC 1918), localhost, or cloud metadata endpoints. This enables Server-Side Request Forgery (SSRF), allowing any user interacting with a publicly exposed chatflow to force the Flowise server to make requests to internal network resources that are inaccessible from the public internet. This vulnerability is fixed in 3.0.13.
- Published
- Mar 10, 2026
- Updated
- Jun 17, 2026
- EPSS
- 2.6% · 86th percentile
- CWE
- CWE-918
Report tools
Action score
36
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.6%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.8
- CNA · GitHub_M
- 7.1
- 1.7 point gap
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| flowiseai | flowise | cpe:2.3:a:flowiseai:flowise |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
FlowiseAI Flowise
- < 3.0.13affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- flowiseai flowisebefore 3.0.13
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | flowise | before 3.0.13 | 3.0.13 |
| npm | flowise-components | before 3.0.13 | 3.0.13 |
Same product
flowiseai: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-59528Flowise has Remote Code Execution vulnerability68This week
- CVE-2025-58434Flowise Cloud and Local Deployments have Unauthenticated Password Reset Token Disclosure that Leads to Account Takeover64This week
- CVE-2025-8943Unsupervised OS command execution leads to remote code execution by unauthenticated network attackers61This week
Published before and after this one in the same product
- ← EarlierCVE-2026-30823Mar 7, 2026 · Flowise: IDOR leading to Account Takeover and Enterprise Feature Bypass via SSO Configuration35Monitor
- ← EarlierCVE-2026-30824Mar 7, 2026 · Flowise: Missing Authentication on NVIDIA NIM Endpoints41Plan
- Later →CVE-2026-40933Apr 21, 2026 · Flowise: Authenticated RCE Via MCP Adapters43Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| FlowiseAI Flowise | 3.0.13 · description | Vendor (CNA) |
| npm:flowise | 3.0.13 | Package registry (OSV) |
| npm:flowise-components | 3.0.13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-91935189 days apartFlowise before 3.1.4 SSRF and API Key Exfiltration via Chat Model Nodes34Monitor
- CVE-2026-4127144 days apartFlowise: APIChain Prompt Injection SSRF in GET/POST API Chains33Monitor
- CVE-2025-59527169 days apartFlowiseAI/Flowise has Server-Side Request Forgery (SSRF) vulnerability32Monitor
- CVE-2026-69257147 days apartFlowise: SSRF Protection Bypass via IPv4-Mapped IPv6 Addresses30Monitor
- CVE-2026-91938189 days apartFlowise before 3.1.4 Server-Side Request Forgery via document loaders30Monitor
- CVE-2026-4127244 days apartFlowise: SSRF Protection Bypass (TOCTOU & Default Insecure)28Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2026-308243 days apartFlowise: Missing Authentication on NVIDIA NIM Endpoints41Plan
- CVE-2026-308213 days apartFlowise: Arbitrary File Upload via MIME Spoofing37Monitor
Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →