Security readout for executives and security teams
Plain-English summary
An authenticated Flowise user can turn a crafted URL value into code execution on servers running versions before 3.1.3. Successful exploitation could expose or alter data and disrupt both Flowise and connected systems accessible to its service account.
Executive priority
Treat as an urgent upgrade for affected installations. Authenticated access lowers exposure compared with an unauthenticated flaw, but successful exploitation could compromise the server and connected resources. Prioritize shared, externally reachable, or highly privileged Flowise deployments.
Technical view
AgentAsTool, ChatflowTool, and ExecuteFlow inserted user-controlled baseURL values into JavaScript executed by in-process vm2. A crafted value could escape the generated string, inject code, escape the sandbox through exposed dependencies, and execute as the Flowise process user. Version 3.1.3 passes the URL as data and strengthens validation.
Likely exposure
Flowise deployments earlier than 3.1.3 are affected when authenticated users can access the vulnerable custom-tool components. Internet-facing or broadly shared instances warrant particular attention, although the supplied sources do not quantify deployment exposure.
Exploitation context
Exploitation requires an authenticated session and is rated high complexity in the supplied CVSS 4.0 vector. The sources describe remote server compromise potential, but provide no evidence of active exploitation; the CVE is not identified as being in KEV.
Researcher notes
The vulnerable pattern is source construction from untrusted baseURL data before vm2 execution. The bundle describes code injection and sandbox escape, while its structured CWE field lists CWE-95. Assess both injection reachability and the privileges available to the Flowise process. No public exploitation evidence is supplied.
Mitigation direction
- Upgrade Flowise to version 3.1.3 or later.
- Restrict authenticated access until upgrading, especially access to custom-tool and flow-building functionality.
- Review Flowise service-account permissions and reduce unnecessary access to secrets, files, networks, and connected systems.
- Follow the Flowise advisory and release guidance for deployment-specific precautions.
Validation and detection
- Confirm every Flowise instance reports version 3.1.3 or later.
- Inventory instances where authenticated users can create or execute the affected custom-tool components.
- Review authentication, flow-change, and server logs for unexpected activity involving affected components or unusual URL values.
- Verify the Flowise process runs with minimal filesystem, network, and credential access after upgrading.
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 lookupCVE-2026-69253 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:H/AT:N/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:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
9CriticalVector: CVSS:4.0/AV:N/AC:H/AT:N/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
- https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-wg86-r78f-74mpCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/FlowiseAI/Flowise/pull/6417CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/FlowiseAI/Flowise/commit/3f257bdc8196082a178da7134a075824401b13b9CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/FlowiseAI/Flowise/releases/tag/flowise@3.1.3CVE reference, GitHub_M · x_refsource_MISC
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.