CVE-2026-69263
Flowise is a drag & drop user interface to build a customized large …
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, the mitigation for CVE-2025-8943 blocked -y and --yes flags on npx, but packages/components/nodes/tools/MCP/core.ts denied only PATH, LD_LIBRARY_PATH, DYLD_LIBRARY_PATH, and NODE_OPTIONS by exact environment-variable name. Because npm reads configuration from npm_config_* variables, setting npm_config_yes=true reproduced --yes behavior without using a blocked flag, causing npx to auto-install and execute the named package when a Custom MCP server launched. This issue is fixed in version 3.1.3.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/FlowiseAI/Flowise/commit/a4c4e4988cded15edf725e762560575b889ae351
- github.com/FlowiseAI/Flowise/pull/6471
- github.com/FlowiseAI/Flowise/releases/tag/[email protected]
- github.com/FlowiseAI/Flowise/security/advisories/GHSA-xc48-889x-5qmw
- github.com/advisories/GHSA-xc48-889x-5qmw
- nvd.nist.gov/vuln/detail/CVE-2026-69263
- cve.org/CVERecord?id=CVE-2026-69263
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.