TL;DR
Langflow ships with a setting, AUTO_LOGIN , that defaults to True . While it is on, an unauthenticated endpoint hands out a superuser session. With that session, the MCP layer can be used to reach Langflow's execute-user-Python feature (custom components). That chain is CVE-2026-110186.
Affected: Langflow OSS 1.0.0 through 1.12.8
Severity: CVSS 3.1 9.8 (Critical), CWE-94 (code injection)
Fixed in: 1.13.0 (released 2026-10-22)
Workaround: none published by IBM
A note on what is confirmed and what is not. The vendor advisory describes CVE-2026-110186 only as improper control of code generation leading to unauthenticated RCE. I could not find a public exploit that executes code on the server, and the public Metasploit module covers the sibling CVE-2026-93680 (auth bypass) and only lists MCP tools. So the first half of the chain (auto-login, MCP enumeration, the patch diff) is based on public source, and step 3 (custom component execution) is a reconstruction from the advisory and that source.…