PatchSiren cyber security CVE debrief
CVE-2026-73602 FlowiseAI CVE debrief
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-13T12:17:24.480Z and has not been modified since then. The NVD entry is currently Awaiting Analysis. The CVE-2026-73602 vulnerability in Flowise before 3.1.3 is a critical sandbox escape issue in the vm2 JavaScript sandbox. This allows authenticated users to execute arbitrary code by exploiting a bypass in moment locale validation. Attackers can craft a fake String object with a match function to bypass path traversal checks, loading and executing malicious JavaScript files stored in the document store outside the sandbox. Flowise users, administrators of Flowise systems, and security teams responsible for patching and vulnerability management should be aware of this critical vulnerability and take immediate action to protect their systems. Authenticated users of Flowise before version 3.1.3 should prioritize patching due to a critical vulnerability allowing arbitrary code execution. Limited information is available on the exact scope of affected systems and potential attack vectors.
- Vendor
- FlowiseAI
- Product
- Flowise
- CVSS
- CRITICAL 9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-13
- Original CVE updated
- 2026-08-31
- Advisory published
- 2026-08-13
- Advisory updated
- 2026-08-31
Who should care
Flowise users, administrators of Flowise systems, and security teams responsible for patching and vulnerability management should be aware of this critical vulnerability and take immediate action to protect their systems.
Technical summary
The CVE-2026-73602 vulnerability in Flowise before 3.1.3 is a critical sandbox escape issue in the vm2 JavaScript sandbox. This allows authenticated users to execute arbitrary code by exploiting a bypass in moment locale validation. Attackers can craft a fake String object with a match function to bypass path traversal checks, loading and executing malicious JavaScript files stored in the document store outside the sandbox.
Defensive priority
Authenticated users of Flowise before version 3.1.3 should prioritize patching due to a critical vulnerability allowing arbitrary code execution.
Recommended defensive actions
- Patch Flowise to version 3.1.3 or later
- Restrict access to Flowise to trusted users only
- Monitor Flowise systems for suspicious activity
- Inventory Flowise installations to ensure version 3.1.3 or later is deployed
- Implement compensating controls to limit potential damage from authenticated users
Evidence notes
The CVE-2026-73602 vulnerability in Flowise before 3.1.3 allows authenticated users to execute arbitrary code via a sandbox escape in the vm2 JavaScript sandbox. The issue arises from a bypass in moment locale validation. Limited information is available on the exact scope of affected systems and potential attack vectors.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-73602 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-73602
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-73602 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-73602
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/FlowiseAI/Flowise/commit/4211bfc8f15746be4019bba557e29a7ba83d54c5
-
Source reference
Unverified legacy reference
URL: https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-rqh4-rxw3-93rp
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/flowise-before-sandbox-escape-to-rce
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.