CVE-2026-55255: Cross-user workflow execution IDOR in Langflow
- Vendor
- Langflow
CVE-2026-55255 is an insecure direct object reference vulnerability in Langflow's OpenAI-compatible Responses API. The get_flow_by_id_or_endpoint_name() helper resolves client-supplied flow UUIDs without verifying ownership by the authenticated requester, unlike its endpoint-name resolution branch. An authenticated user can therefore invoke another user's workflow by supplying its UUID in the model parameter. The workflow executes using the victim's configured credentials and integrations, potentially exposing sensitive data and embedded secrets. The primary affected-version range is Langflow releases before 1.9.1, although some affected-version information extends the range to releases before 1.9.2. Exploitation was observed beginning June 25, 2026, and CISA added the vulnerability to its Known Exploited Vulnerabilities catalog on July 7, 2026.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation breaks user and tenant isolation, allowing unauthorized workflow execution, access to sensitive workflow outputs, and consumption of victim resources. Depending on workflow behavior, attackers may extract LLM-provider API keys, cloud credentials, database secrets, or other sensitive information available to the workflow. Exposed credentials can enable downstream access to connected services within their granted permissions. This vulnerability alone does not establish arbitrary operating-system command execution.
Mitigation
If you can’t patch tonight, do this now.
Until patched, restrict or disable access to the Responses API, limit deployment access to trusted users and networks, and remove unnecessary internet exposure. Monitor for flow identifiers that do not belong to the authenticated requester and unexpected workflow executions. Authentication alone is insufficient because ordinary authenticated users can exploit the flaw.
Remediation
Patch, then assume compromise.
Upgrade to a current supported Langflow release. The ownership-check fix is identified as introduced in 1.9.1, but conflicting affected-version information identifies 1.9.2 as the fixed release; use 1.9.2 or later to cover both stated boundaries. The fix must enforce ownership or equivalent authorization for UUID-based flow resolution as well as endpoint-name-based resolution. Review historical executions for cross-user access and rotate potentially exposed provider keys, cloud credentials, and database secrets.
Exploits
No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-55255 exploited in the wild?
- Yes. As of Oct 20, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Jul 7, 2026.
- Is there a public exploit for CVE-2026-55255?
- Yes. As of Oct 20, 2026, Mallory has reports of a public exploit for CVE-2026-55255.
- Is there a patch for CVE-2026-55255?
- Upgrade to a current supported Langflow release. The ownership-check fix is identified as introduced in 1.9.1, but conflicting affected-version information identifies 1.9.2 as the fixed release; use 1.9.2 or later to cover both stated boundaries.
- What products are affected by CVE-2026-55255?
- Langflow.
- How severe is CVE-2026-55255?
- CVE-2026-55255 has a CVSS v3.1 score of 8.4 (High) and an EPSS score of 0.89% (60th percentile) as of Oct 20, 2026.
Recent activity
110 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.