CVEReports
CVEReports

Automated vulnerability intelligence platform. Comprehensive reports for high-severity CVEs generated by AI.

Product

  • Home
  • Sitemap
  • RSS Feed

Company

  • About
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 CVEReports. All rights reserved.

Made with love by Amit Schendel & Alon Barad



CVE-2026-31829

CVE-2026-31829: Server-Side Request Forgery in Flowise HTTP Node

Alon Barad
Alon Barad
Software Engineer

Mar 11, 2026·5 min read·123 visits

Executive Summary (TL;DR)

High-severity SSRF in Flowise < 3.0.13 via unvalidated HTTP Node URLs allows internal network scanning and metadata exfiltration. Fixed in 3.0.13 via IP blocklisting.

Flowise versions prior to 3.0.13 are vulnerable to a High-severity Server-Side Request Forgery (SSRF) flaw in the HTTP Node component. Attackers with access to modify chatflows can force the server to execute unauthorized requests against internal network boundaries, cloud metadata endpoints, and local services.

Vulnerability Overview

Flowise is a drag-and-drop user interface designed for building customized large language model (LLM) workflows. The core functionality relies on various nodes that connect APIs, local models, and external services to facilitate complex data processing pipelines. Within these workflows, the AgentFlow and Chatflow components utilize an HTTP Node to perform server-side requests to external endpoints.

CVE-2026-31829 identifies a Server-Side Request Forgery (SSRF) vulnerability within this HTTP Node implementation. In versions prior to 3.0.13, the application fails to validate or restrict the target URLs supplied to the node. This architectural flaw permits users to specify arbitrary destinations, which the backend server will dutifully query without considering the network boundaries or security context of the target.

The resulting impact is substantial, as it transforms the Flowise server into an unauthenticated proxy for malicious actors. Attackers can leverage this capability to bypass external firewalls, interact with loopback interfaces, and access sensitive internal services that are otherwise protected from internet-facing traffic.

Root Cause Analysis

The root cause of CVE-2026-31829 lies in the absence of input sanitization and destination validation within the HTTP Node's execution logic. When a workflow is triggered, the node extracts the user-defined URL from its configuration properties and passes it directly to the underlying HTTP client library. The application does not perform preliminary checks against the resolved IP address or the hostname structure.

In a secure implementation, an application performing outbound web requests must perform DNS resolution on the target hostname and compare the resulting IP address against a strict allowlist or blocklist. Flowise versions prior to 3.0.13 omit this critical validation phase. Consequently, the application initiates TCP connections regardless of whether the resolved IP address resides in a restricted network space, such as an RFC 1918 private subnet or a loopback address.

Furthermore, the application lacks protections against DNS rebinding attacks or redirects to internal services. The HTTP client blindly follows the protocol instructions provided by the user input, allowing access to administrative panels, local databases, or cloud provider metadata endpoints that rely solely on network-level segmentation for security.

Exploitation and Attack Vectors

Exploitation of CVE-2026-31829 requires the attacker to possess the ability to create or modify a flow within the Flowise environment. This prerequisite is met if the attacker has authenticated access to the management interface or if a specific chatflow is publicly exposed and permits user-driven modifications. The required privileges are classified as low, as any user capable of interacting with the flow designer can orchestrate the attack.

The attack methodology begins with the construction of a malicious workflow. The attacker inserts an HTTP Node and configures the target URL parameter to point to a restricted internal endpoint. High-value targets typically include http://169.254.169.254/latest/meta-data/ for AWS EC2 instance metadata, http://localhost:11434 for local Ollama instances, or standard private IP ranges such as 10.0.0.0/8.

Upon executing the flow, the Flowise backend processes the node and issues the HTTP GET or POST request to the specified internal address. The server captures the HTTP response from the targeted internal resource and returns it to the attacker through the flow's standard output mechanism. This allows the attacker to read the contents of the response, completing the data exfiltration cycle.

Impact Assessment

The primary consequence of this SSRF vulnerability is the complete circumvention of network perimeter defenses. By forcing the Flowise application to act as a proxy, attackers gain the ability to interact with the internal network environment from the perspective of the compromised server. This invalidates firewall rules and Access Control Lists (ACLs) designed to protect internal assets from external interaction.

The highest severity risk involves the compromise of cloud infrastructure via the instance metadata service (IMDS). If the Flowise application is hosted on an AWS EC2 instance or an equivalent cloud compute environment, querying 169.254.169.254 permits the exfiltration of temporary Identity and Access Management (IAM) credentials. These credentials facilitate lateral movement into the broader cloud account, potentially leading to widespread data breaches or infrastructure takeover.

Additionally, the vulnerability supports systematic internal network reconnaissance. Attackers can automate requests across private IP ranges to perform port scanning and service enumeration. This activity identifies secondary targets, such as unauthenticated internal administrative interfaces, databases, or microservices, paving the way for further exploitation and deeper network compromise.

Remediation and Patch Implementation

The vulnerability is officially remediated in Flowise version 3.0.13. The maintainers addressed the flaw by introducing a comprehensive host restriction policy within the HTTP Node's execution path. This patch intercepts outbound requests and validates the target destination prior to initiating the network connection.

The technical fix implements a default blocklist that denies access to common internal and private network addresses, including loopback interfaces and RFC 1918 IP spaces. To provide operational flexibility, the patch also introduces a new environment variable named HTTP_DENY_LIST. This variable allows systems administrators to define custom blocklists, enabling the restriction of specific hostnames or IP subnets tailored to their unique deployment environment.

When the patched application detects an attempt to query a restricted address, it gracefully aborts the connection and returns a standardized error message: "Error: Access to this host is denied by policy." Organizations utilizing Flowise must upgrade to version 3.0.13 immediately. Administrators should subsequently review their integrations, as the default deny policy may disrupt legitimate workflows that rely on accessing local services, as documented in user reports following the patch release.

Official Patches

FlowiseAIGitHub Security Advisory GHSA-fvcw-9w9r-pxc7
FlowiseAIBugfix/Securely Fetch Links (PR #5200)

Technical Appendix

CVSS Score
7.1/ 10
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L

Affected Systems

Flowise AgentFlowFlowise ChatflowFlowise HTTP Node

Affected Versions Detail

Product
Affected Versions
Fixed Version
Flowise
FlowiseAI
< 3.0.133.0.13
AttributeDetail
CWE IDCWE-918
Attack VectorNetwork
CVSS Score7.1
ImpactHigh (Confidentiality & Integrity)
Exploit StatusProof of Concept Available
Patch Version3.0.13

MITRE ATT&CK Mapping

T1190Exploit Public-Facing Application
Initial Access
T1005Data from Local System
Collection
CWE-918
Server-Side Request Forgery (SSRF)

The web application does not validate or incorrectly validates user-provided URLs before making a request to the designated resource.

Vulnerability Timeline

Flowise version 3.0.13 released containing the SSRF protection fix via PR #5200.
2026-02-03
Users report issues accessing internal services due to the new default deny policy (Issue #5785).
2026-02-19
CVE-2026-31829 and GHSA-fvcw-9w9r-pxc7 officially published.
2026-03-10

References & Sources

  • [1]GitHub Security Advisory GHSA-fvcw-9w9r-pxc7
  • [2]NVD Record CVE-2026-31829
  • [3]Flowise Issue #5785 - Error: Access to this host is denied by policy
  • [4]Flowise PR #5200 - Bugfix/Securely Fetch Links

Attack Flow Diagram

Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

More Reports

•about 19 hours ago•CVE-2026-58254
6.5

CVE-2026-58254: Authorization Bypass in NATS Server Message Tracing for Leaf Node Connections

NATS Server prior to versions 2.12.8 and 2.14.3 contains an incorrect authorization vulnerability (CWE-863) in its message tracing subsystem. When evaluating whether a connection is permitted to publish trace events to a destination subject specified in the Nats-Trace-Dest header, the server only checks standard client permissions and omits permission checks for leaf node connections. This allows a connected leaf node operator with restricted publishing privileges to emit internal trace events to unauthorized subjects and suppress standard message delivery using the Nats-Trace-Only header.

Alon Barad
Alon Barad
4 views•10 min read
•about 20 hours ago•CVE-2026-63341
7.5

CVE-2026-63341: Unauthenticated Denial of Service via Unbounded Topic Depth in Aedes MQTT Broker

CVE-2026-63341 is a high-severity Denial of Service (DoS) vulnerability in the Aedes MQTT broker for Node.js affecting all versions prior to 1.1.1. The flaw stems from missing input validation on the hierarchical depth of incoming MQTT topic strings before they are passed to the underlying topic-matching engine, qlobber. Because qlobber enforces a hardcoded limit of 100 topic levels and throws a synchronous exception when this threshold is exceeded, an attacker can send a single MQTT packet containing 101 or more forward-slash-separated levels to trigger an uncaught exception that immediately terminates the Node.js broker process.

Alon Barad
Alon Barad
8 views•12 min read
•about 21 hours ago•CVE-2026-61725
6.1

CVE-2026-61725: Path Traversal and Arbitrary File Overwrite in sevenz-rust2

CVE-2026-61725 is a path traversal vulnerability (CWE-22) in the sevenz-rust2 Cargo package prior to version 0.21.1. The vulnerability occurs because the decompression utility fails to validate or sanitize archive entry filenames before joining them with the destination directory path via std::path::Path::join. An attacker who supplies a crafted 7z archive containing parent directory traversal sequences or absolute paths can write or overwrite arbitrary files on the host filesystem with the privileges of the extracting process.

Alon Barad
Alon Barad
5 views•12 min read
•about 22 hours ago•CVE-2026-77309
8.8

CVE-2026-77309: Unauthenticated Remote Code Execution in NASA-AMMOS AIT-GUI via Incomplete File Cleanup and Path Traversal

CVE-2026-77309 (GHSA-jrjx-9jjw-747m) is a high-severity unauthenticated remote code execution vulnerability affecting NASA-AMMOS AIT-GUI versions 1.0.0 through 2.5.0. The flaw results from chaining an incomplete file cleanup error in the telemetry query endpoint (/tlm/query) with a directory traversal flaw in the script execution endpoint (/script/run). An attacker on an adjacent network can stage arbitrary Python statements into a static file on disk and execute that file under the privileges of the AIT-GUI web server process.

Amit Schendel
Amit Schendel
10 views•10 min read
•about 23 hours ago•CVE-2026-77332
2.3

CVE-2026-77332: Surfaced-Memory Envelope Injection and Stored Prompt Injection in memtomem-stm

A vulnerability classified under CWE-116 (Improper Encoding or Escaping of Output) exists in memtomem-stm versions 0.1.0 through 0.1.33. The software acts as a Model Context Protocol (MCP) short-term memory proxy gateway for AI agent architectures. When surfacing retrieved memories and scratchpad items into downstream Large Language Model (LLM) context envelopes, the SurfacingFormatter component fails to properly sanitize untrusted memory attributes. An attacker with the ability to plant untrusted content into the agent's long-term or working memory store can inject arbitrary structural delimiters, close the <surfaced-memories> XML boundary prematurely, visually obscure instructions using Unicode bidirectional overrides, and execute stored prompt injection attacks against downstream LLM agents.

Alon Barad
Alon Barad
12 views•10 min read
•1 day ago•CVE-2026-77331
2.0

CVE-2026-77331: Race Condition and Session State Corruption in memtomem-stm

CVE-2026-77331 (GHSA-72jh-722p-rqr3) is a concurrency and session-state synchronization vulnerability in memtomem-stm, a short-term memory proxy gateway for AI agents. In versions 0.1.2 prior to 0.1.34, concurrent Model Context Protocol (MCP) Remote Procedure Call (RPC) failures or mid-flight task cancellations can initiate duplicate reconnect loops and permit dirty or cancelled transport sessions to be reused. This deficiency results in session-state integrity loss and local service degradation.

Amit Schendel
Amit Schendel
6 views•9 min read