Security readout for executives and security teams
Plain-English summary
An authenticated Flowise user can break out of a JavaScript safety boundary and run code on the server. Successful exploitation could expose or alter sensitive data, disrupt service, and affect connected systems. Flowise installations older than 3.1.3 should be treated as urgent upgrade candidates.
Executive priority
Prioritize remediation immediately because successful exploitation provides server-side code execution and potentially broad business impact. First identify externally reachable and multi-user Flowise deployments, upgrade them, and assess vulnerable hosts for compromise. Active exploitation is not confirmed, but the consequence and low privilege requirement justify urgent action.
Technical view
The flaw affects Flowise's vm2 sandbox. A crafted String-like object can bypass moment locale path validation, allowing JavaScript stored outside the sandbox in the document store to be loaded and executed. Exploitation is network-accessible, requires low privileges and additional preparation, and can compromise confidentiality, integrity, and availability.
Likely exposure
Exposure is highest where Flowise versions before 3.1.3 are network-accessible and untrusted or weakly governed users can authenticate. Risk depends on attackers satisfying the additional document-store preparation condition. Internet exposure is not required if a malicious or compromised internal account can reach the application.
Exploitation context
The supplied CVSS 4.0 score is 9.0, with low attack complexity, low privileges, no user interaction, and an additional attack prerequisite. The source bundle does not identify CISA KEV listing or provide evidence of active exploitation. Exploitation in the wild should therefore be treated as unconfirmed.
Researcher notes
CWE-95 applies. The bundle's affected-version array is internally ambiguous, listing "0" and "3.1.3" with a default unaffected status, while the title and description consistently state versions before 3.1.3. Confirm exact version boundaries against the vendor advisory. No exploit maturity or observed campaign information is supplied.
Mitigation direction
- Upgrade Flowise to version 3.1.3 or later following the vendor advisory.
- Until upgraded, restrict Flowise access to trusted users and reduce unnecessary network exposure.
- Review the vendor patch and guidance for deployment-specific remediation requirements.
- Investigate potentially compromised systems before returning vulnerable instances to normal service.
Validation and detection
- Inventory every Flowise deployment and record its exact running version.
- Confirm all production and development instances run Flowise 3.1.3 or later.
- Review authenticated-user activity and document-store contents for unexplained JavaScript files or execution indicators.
- Verify access restrictions prevent untrusted accounts from reaching remaining vulnerable instances.
- Check host and application telemetry for unexpected processes, file changes, or outbound connections.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-95: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-73602 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9CriticalVector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-rqh4-rxw3-93rp)CVE reference, VulnCheck · vendor-advisory
- Patch CommitCVE reference, VulnCheck · patch
- VulnCheck Advisory: Flowise before 3.1.3 Sandbox Escape to RCECVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.