Skip to main content
EPSS 0.5%top 60%

CVE-2026-69263: CWE-184: Incomplete List of Disallowed Inputs in FlowiseAI Flowise

0
High
VulnerabilityCVE-2026-69263cvecve-2026-69263cwe-184
Published: 08/04/2026 (08/04/2026, 16:54:36 UTC)
Source: CVE Database V5
Vendor/Project: FlowiseAI
Product: Flowise

Description

Flowise versions prior to 3.1.3 have an incomplete mitigation for a security issue where certain environment variables were not blocked, allowing unintended automatic package installation via npx when launching a Custom MCP server. This vulnerability is identified as CVE-2026-69263 and is fixed in version 3.1.3.

CVSS v4.0

Score 8.7high

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vuln. Confidentiality
High
Vuln. Integrity
High
Vuln. Availability
High
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Affected software

FlowiseAI

Flowise

Affected versions
<3.1.3
GitHub Actionsmore threats →ai
flowiseai/Flowise
pkg:github/flowiseai/Flowise
Affected versions
<3.1.3

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 08/11/2026, 18:18:32 UTC

Technical Analysis

Flowise, a drag-and-drop interface for building customized large language model flows, had a vulnerability (CVE-2026-69263) due to incomplete filtering of environment variables controlling npx behavior. While prior mitigation blocked the -y and --yes flags on npx, it did not block npm_config_yes environment variables, which can trigger the same automatic package installation behavior. This allowed an attacker to cause npx to auto-install and execute arbitrary packages when a Custom MCP server launched. The issue is resolved in Flowise version 3.1.3.

Potential Impact

An attacker with the ability to set environment variables could bypass existing mitigations and cause npx to automatically install and execute arbitrary packages, potentially leading to code execution in the context of the Flowise application. This elevates the risk of unauthorized code execution and compromise of the affected system.

Mitigation Recommendations

Upgrade Flowise to version 3.1.3 or later, where this vulnerability is fixed. No other official remediation or temporary fixes are documented. Patch status is not explicitly stated but the fix is included in version 3.1.3.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-08-03T19:54:19.853Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6a721d52bf8831d53928c602

Added to database: 08/04/2026, 17:11:46 UTC

Last enriched: 08/11/2026, 18:18:32 UTC

Last updated: 09/18/2026, 02:30:21 UTC

Views: 53

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses