Security readout for executives and security teams
Plain-English summary
An authenticated Flowise user could abuse the SQLite Record Manager node to write attacker-controlled data outside its intended location. In affected Docker deployments running as root, this could lead to operating-system command execution and complete compromise of the service, its data, and connected resources.
Executive priority
Treat affected, root-running Docker deployments as an emergency upgrade, especially when workflow-building interfaces are externally reachable. Successful exploitation could provide full service and host compromise. Other affected installations still warrant expedited remediation because authenticated access is the principal stated prerequisite.
Technical view
Before 3.1.3, user-controlled additionalConfig could override the intended SQLite database path. With the published root-running Docker image, an authenticated attacker could place crafted database content where Chromium configuration files were loaded, resulting in code execution when Puppeteer launched Chromium. The issue is classified as CWE-94 with CVSS 4.0 score 9.4.
Likely exposure
Flowise versions earlier than 3.1.3 are affected. Risk is greatest where authenticated users can create or modify flows using SQLite Record Manager and the published Docker image runs as root. The supplied evidence does not establish exposure for installations using different runtime permissions or configurations.
Exploitation context
Exploitation requires authenticated access but no user interaction, and the supplied CVSS vector rates attack complexity as low. The source bundle reports no CISA KEV listing and provides no evidence of active exploitation. Absence from KEV does not prove exploitation has not occurred.
Researcher notes
The vulnerable merge order allowed additionalConfig.database to replace the intended path. The demonstrated impact depends on filesystem permissions, attacker-controlled record content, and Chromium loading configuration from the written location. The supplied sources establish a fix in 3.1.3 but do not provide evidence of exploitation in the wild.
Mitigation direction
- Upgrade every affected Flowise deployment to version 3.1.3 or later.
- Prioritize affected deployments using the published Docker image or running Flowise as root.
- Until upgraded, restrict flow-building access and follow any additional Flowise vendor guidance.
- Isolate potentially compromised instances and apply established incident-response procedures.
Validation and detection
- Inventory Flowise deployments and confirm each installed version.
- Identify deployments using the published Docker image and determine their runtime user privileges.
- Review access controls for users able to create or modify Flowise workflows.
- Check affected hosts for unexpected filesystem writes or suspicious Chromium and Puppeteer activity.
- Confirm version 3.1.3 or later after remediation and retest normal workflow operation.
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-94: 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 lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique 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-69259 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 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/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:L/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
9.4CriticalVector: CVSS:4.0/AV:N/AC:L/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-x3hf-7cj6-3r4mCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/FlowiseAI/Flowise/pull/6464CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/FlowiseAI/Flowise/commit/d07186844263bad057008863037466aff7c3390fCVE 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 Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.