Security readout for executives and security teams
Plain-English summary
Flowise versions before 3.1.3 can mistake visually similar Unicode characters for harmless input. Python later interprets those characters as blocked names, enabling an attacker to escape the intended restrictions and potentially execute operating-system commands on the Flowise host.
Executive priority
Treat this as an urgent remediation for any Flowise deployment below 3.1.3, especially internet-accessible or multi-user systems. Successful exploitation could compromise confidentiality, integrity, and availability of the host and connected systems. Prioritize version inventory, access restriction, upgrade, and post-upgrade review for suspicious activity.
Technical view
The affected validator uses ASCII-only JavaScript word boundaries to blacklist dangerous Python identifiers. Python 3 normalizes identifiers using NFKC, allowing Unicode homoglyphs to bypass validation while parsing as blocked ASCII identifiers. Affected CSVAgent and AirtableAgent paths pass validated code to Pyodide, whose JavaScript interop can reach the host operating system.
Likely exposure
Exposure is limited to Flowise versions earlier than 3.1.3. Risk is greatest where affected CSVAgent or AirtableAgent functionality is reachable and attacker-controlled Python can reach the validator. The supplied sources do not establish how commonly these agents are enabled or externally exposed.
Exploitation context
The CVSS 4.0 assessment is 9.5 and indicates network reachability, no required privileges, no user interaction, and high impact, although attack complexity is high. The source bundle reports no KEV listing and provides no evidence of active exploitation.
Researcher notes
CWE-184 applies because the validation logic handles equivalent character forms inconsistently. The key mismatch is ASCII-oriented JavaScript boundary matching versus Python identifier normalization. The advisory states the result can progress from arbitrary Pyodide Python execution to host command execution through JavaScript module interop. No exploitation telemetry is supplied.
Mitigation direction
- Upgrade Flowise to version 3.1.3 or later.
- Restrict access to affected Flowise agent functionality until upgrading.
- Check the Flowise advisory for additional vendor guidance if immediate upgrading is impossible.
- Review host credentials and privileges available to the Flowise process.
Validation and detection
- Confirm every deployed Flowise instance reports version 3.1.3 or later.
- Inventory workflows using CSVAgent or AirtableAgent nodes.
- Verify older instances are inaccessible to untrusted users pending upgrade.
- Review available input history for suspicious non-ASCII Python identifiers.
- Investigate unexpected child processes or operating-system command activity from Flowise hosts.
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-184: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCVE-2026-70470 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.5 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/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:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
9.5CriticalVector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/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-52fh-8v99-63c2CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/FlowiseAI/Flowise/pull/6499CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/FlowiseAI/Flowise/commit/f4e2794f6a576b94578f2fdafbf49c2fb304626cCVE 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.
Incomplete List of Disallowed Inputs
Incomplete List of Disallowed Inputs represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.