Flowise Sandbox Escape to RCE

Answer in brief

CVE-2026-69253 records a Critical severity (CVSS 9.0) vulnerability in Flowise Sandbox Escape to RCE. The current sources do not mark it as known exploited. The current feed maps FlowiseAI/Flowise (generic), flowise (npm), flowise-components (npm). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 4, 2026Updated Sep 8, 2026Source checked Sep 18, 2026First seen by HOL Aug 4, 2026Material review Sep 8, 2026

Upstream Advisory

Key facts

Risk: Critical · CVSS 9.0
Exploitation: Not marked as known exploited
Affected software: 3 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 9.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps FlowiseAI/Flowise (generic), flowise (npm), flowise-components (npm). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
FlowiseAI/Flowisegeneric	< 3.1.3	Not reported
flowisenpm	<=3.1.2	3.1.3
flowise-componentsnpm	<=3.1.2	3.1.3

Recommended response

Check inventory. Check lockfiles and deployed manifests for FlowiseAI/Flowise, flowise, flowise-components.
Review the reported fix. Update flowise to 3.1.3; flowise-components to 3.1.3 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 8, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 4, 2026

Sources and claim methodology

Upstream source description

Flowise is a drag-and-drop user interface for building customized large language model (LLM) flows. Prior to version 3.1.3, several custom-tool components — AgentAsTool, ChatflowTool, and ExecuteFlow — ran code in the in-process vm2 sandbox. To build that code, they inserted a user-controlled baseURL value straight into the JavaScript source, for example const url = "${baseURL}/..."; . The only check on baseURL was isValidURL , but a valid-looking URL can still contain characters that break out of a code string. An authenticated user could craft a baseURL that passed this check, closed the surrounding string, and injected their own JavaScript into the sandboxed script (code injection, CWE-94). The vm2 sandbox runs in the same Node.js process as Flowise and exposes risky dependencies. As a result, the injected code could escape the sandbox and run arbitrary code on the Flowise server as the Flowise process user. Exploitation only requires an authenticated session. The issue is fixed in version 3.1.3, which passes the URL to the sandbox as data instead of inserting it into code and adds stricter URL validation.

Quoted source text, attributed separately from HOL analysis.