CVE-2026-46442
A security flaw in Flowise allows authenticated users to bypass security boundaries and run unauthorized commands on the server. This occurs because a specific feature lacks proper authorization checks and uses a sandbox that can be escaped.
An official fix is available, so this entry is kept for 30 days and then removed automatically.
Who is affected
Users running Flowise versions prior to 3.1.2, particularly those using the default deployment configuration without an E2B_APIKEY.
Real-world impact
An attacker with basic access or an API key can execute arbitrary system commands on the server hosting Flowise, potentially taking full control of the host machine.
Why this severity
The critical score reflects that an attacker can remotely execute code on the host system with high impact, requiring only basic authentication to exploit.
What to do about it
- 01Upgrade Flowise to version 3.1.2 or later.
NVD-referenced vendor advisory
Timeline
- Jun 8, 2026 · Jun 8, 2026PublishedDisclosed and added to the National Vulnerability Database.
- Jul 23, 2026 · 12d agoAdvisory updatedThe NVD record was last revised.
- Jul 24, 2026 · 11d agoOfficial fix availableA vendor patch or mitigation now exists — see the remediation steps above.
How it’s attacked
References & advisories
- github.com/FlowiseAI/Flowise/releases/…productrelease notes
- github.com/FlowiseAI/Flowise/security/…exploitmitigationvendor advisory