CVE-2026-41268: Flowise Parameter Override Bypass Leading to Unauthenticated RCE
Flowise versions before 3.1.0 contain a critical flaw that allows unauthenticated remote command execution through a parameter override bypass combined with environment variable injection. According to the record, a single HTTP request can run arbitrary commands with root privileges inside the containerized instance. Upgrading to 3.1.0 or later is the primary remediation, and no confirmed exploitation in the wild appears in the sources consulted.
Overview
Flowise is a drag and drop interface for building customized large language model flows. This record describes a critical flaw in versions before 3.1.0 that can allow unauthenticated remote command execution through a parameter override bypass combined with an environment variable injection.
Impact
- According to the record, a single HTTP request is enough to run arbitrary system commands.
- Commands run with root privileges inside the containerized Flowise instance.
- NVD assigns a CVSS score of 9.8 (critical), and the SSVC technical impact is recorded as total.
Affected products and versions
- Product: Flowiseai Flowise.
- Affected: versions before 3.1.0.
- Fixed in: 3.1.0, as stated in the record description.
The structured fixes list in the record is empty, so the fix version comes from the description and should be confirmed against the vendor advisory.
Exploitation status
The record shows this CVE is not listed in the CISA KEV catalog, so no active exploitation is recorded there. The SSVC data records exploitation as proof of concept, and the vendor advisory reference is tagged as exploit-related. No confirmed exploitation in the wild appears in the sources consulted.
Remediation and mitigation
- Upgrade Flowise to 3.1.0 or later as the primary action.
- Until the upgrade is applied, reduce exposure by keeping the instance away from untrusted networks and restricting access to its flow and administrative endpoints.
- Review the container configuration and the privileges the container runs with, since the record describes root-level execution.
- Consult the official GitHub security advisory for vendor guidance.
Detection guidance
- Review web server and application logs for unusual requests to the instance from unknown sources.
- Monitor the container for unexpected child processes, outbound connections, or changes to environment configuration.
- Treat any sign of compromise as an incident and rotate credentials the instance could access.
Limitations of the available information
- The record does not confirm the exact request conditions or whether a public proof of concept is fully available, and this analysis does not provide them.
- The record gives no affected versions beyond the range before 3.1.0 and no additional fix details.
- The EPSS entry carries a date of 2026-10-23, which should be checked against the source before it is relied upon.
Frequently asked questions
Which Flowise versions are affected?
According to the record, versions before 3.1.0 are affected, and the vulnerability is fixed in 3.1.0.
Does this flaw require authentication?
The record describes it as unauthenticated and exploitable with a single HTTP request, which is why it is rated critical.
Is this CVE known to be exploited in the wild?
It is not listed in the CISA KEV catalog in the record, and no confirmed exploitation appears in the sources consulted. The SSVC data records a proof of concept.
What should administrators do first?
Upgrade Flowise to 3.1.0 or later, and in the meantime restrict network exposure and review the privileges of the container.
This analysis was drafted with AI assistance from verified source data and automatically checked against it.