CVE-2026-70470: CWE-184: Incomplete List of Disallowed Inputs in FlowiseAI Flowise
Flowise versions prior to 3.1.3 contain a vulnerability in the Python code validation logic that allows bypass using Unicode homoglyph identifiers. This bypass enables arbitrary Python code execution inside Pyodide and full OS command execution on the host via Pyodide JavaScript module interop. The issue arises because the validator uses an ASCII-only blacklist with JavaScript regex word boundaries, which do not account for Unicode normalization performed by Python. This vulnerability is fixed in version 3.1.3.
AI Analysis
Technical Summary
Flowise's validatePythonCodeForDataFrame function uses an ASCII word-boundary blacklist to restrict certain Python identifiers. However, due to the difference in Unicode normalization between JavaScript regex and Python parsing, attackers can use Unicode homoglyphs (characters visually similar to ASCII but different code points) to bypass the blacklist. This allows execution of arbitrary Python code within Pyodide and consequently full OS command execution on the Flowise host through Pyodide's JavaScript interop. The vulnerability is identified as CWE-184 (Incomplete List of Disallowed Inputs) and has a CVSS 4.0 score of 9.5 (critical). The issue is resolved in Flowise version 3.1.3.
Potential Impact
Successful exploitation allows unauthenticated attackers to execute arbitrary Python code within the Pyodide environment and escalate to full OS command execution on the Flowise host. This can lead to complete compromise of the host system running Flowise versions prior to 3.1.3.
Mitigation Recommendations
Upgrade Flowise to version 3.1.3 or later, where this vulnerability is fixed. No other mitigation or workaround is documented. Patch status is not explicitly stated but the vendor has fixed the issue in version 3.1.3.
CVE-2026-70470: CWE-184: Incomplete List of Disallowed Inputs in FlowiseAI Flowise
Description
Flowise versions prior to 3.1.3 contain a vulnerability in the Python code validation logic that allows bypass using Unicode homoglyph identifiers. This bypass enables arbitrary Python code execution inside Pyodide and full OS command execution on the host via Pyodide JavaScript module interop. The issue arises because the validator uses an ASCII-only blacklist with JavaScript regex word boundaries, which do not account for Unicode normalization performed by Python. This vulnerability is fixed in version 3.1.3.
CVSS v4.0
Score 9.5critical
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Flowise's validatePythonCodeForDataFrame function uses an ASCII word-boundary blacklist to restrict certain Python identifiers. However, due to the difference in Unicode normalization between JavaScript regex and Python parsing, attackers can use Unicode homoglyphs (characters visually similar to ASCII but different code points) to bypass the blacklist. This allows execution of arbitrary Python code within Pyodide and consequently full OS command execution on the Flowise host through Pyodide's JavaScript interop. The vulnerability is identified as CWE-184 (Incomplete List of Disallowed Inputs) and has a CVSS 4.0 score of 9.5 (critical). The issue is resolved in Flowise version 3.1.3.
Potential Impact
Successful exploitation allows unauthenticated attackers to execute arbitrary Python code within the Pyodide environment and escalate to full OS command execution on the Flowise host. This can lead to complete compromise of the host system running Flowise versions prior to 3.1.3.
Mitigation Recommendations
Upgrade Flowise to version 3.1.3 or later, where this vulnerability is fixed. No other mitigation or workaround is documented. Patch status is not explicitly stated but the vendor has fixed the issue in version 3.1.3.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-04T15:24:41.338Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a722805bf8831d53935abe8
Added to database: 08/04/2026, 17:57:25 UTC
Last enriched: 08/04/2026, 18:11:48 UTC
Last updated: 08/04/2026, 18:11:48 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.