Langflow 1.0.0 Through 1.12.8 Is Affected, and IBM Names 1.13.0 as the Only Fix
IBM's security bulletin says every Langflow release from 1.0.0 through 1.12.8 is affected, with no interim workaround and version 1.13.0 as the only fix.

IBM has told users of Langflow to upgrade now. The company published a security bulletin on 28 October 2026 and updated it on 29 October. It covers four flaws in Langflow, an open-source tool for building AI agents and workflows, and three in Hono, a web framework that Langflow bundles.
The Hacker News reported the bulletin. The two most serious flaws, both rated 9.8 by IBM, include an unauthenticated route to running arbitrary code on a server.
Four Langflow Flaws and Three Dependency Issues
CVE-2026-93680 is an authentication bypass rated 9.8 that a remote attacker can use without credentials. CVE-2026-110186, also rated 9.8, lets an unauthenticated remote attacker run arbitrary code because code generation is improperly controlled.
CVE-2026-110193, rated 8.8, lets an attacker with a low-privileged account get the Agentic Assistant to generate component code that runs operating system commands on the server. CVE-2026-110192, rated 6.5, exposes insufficiently protected credentials to a remote authenticated attacker.
The three Hono issues carry GitHub ratings in the bulletin. CVE-2026-84363 (5.9) can enable cache poisoning. CVE-2026-84364 (5.3) can exhaust memory, but only where dot-notation form parsing is enabled, which is not the default. CVE-2026-84365 (6.5) can write files outside the output directory during static site generation.
Affected Versions, a Disputed Range and Automatic Login
IBM lists every Langflow OSS release from 1.0.0 through 1.12.8 as affected on Windows, Linux and macOS. The fix is version 1.13.0, which The Hacker News gives a release date of 22 October. Version 1.12.8 was released the same day and still carries the flaws.
For servers that cannot upgrade yet, IBM provides no workaround.
The author of a public Metasploit module lists a narrower affected range, 1.5.0 through 1.11.4, than IBM's 1.0.0 through 1.12.8, according to The Hacker News.
The Hacker News says Langflow 1.12.8 enables automatic login by default, which signs users in as superusers without a prompt, and that version 1.13 turns it off by default. The Hacker News says IBM's bulletin does not say whether servers with automatic login turned off are vulnerable.
IBM also published CVE records for 29 other Langflow flaws on 29 October, naming versions 1.12.4 and 1.12.5 as fixes. One of them, CVE-2026-104339, could let an unauthenticated attacker run code and is rated 9.8. The Hacker News says none of the 33 records lists 1.13.0 as affected.
Exploitation Status and Earlier CISA Listings
As of CISA's 30 October update, neither of the two critical Langflow flaws was in the Known Exploited Vulnerabilities catalog, according to The Hacker News. Six other Langflow flaws are listed there. The most recent, CVE-2026-9198, a 9.8 code injection flaw fixed in version 1.10.1 in July, was added on 5 August 2026.
When CISA added CVE-2026-9198, it gave federal civilian agencies until 7 August to apply fixes. The Hacker News, citing KEVIntel telemetry, reported 650 exploitation attempts from 244 IP addresses in 41 countries starting 6 July 2026, as of August 2026.
A public Metasploit module cites CVE-2026-93680. It connects to a Langflow server's MCP endpoint without credentials and lists the server's tools. The Hacker News says the module does not run code or commands, and that it was tested on Langflow 1.8.4 with automatic login turned on.
“For servers that cannot upgrade yet, IBM provides no workaround.”
What Operators Should Do Before Upgrading
Back up the database, the secret key and uploaded files first. If the server uses automatic login, prepare the existing account for password sign-in before upgrading, following Langflow's upgrade guidance.
Upgrade with pip using langflow==1.13.0, or move Docker deployments to the 1.13.0 image while keeping persistent data. The Hacker News advises against deleting or reinstalling Langflow to fix sign-in problems, because Langflow's documentation warns this can permanently remove flows.
IBM says it "strongly recommends" upgrading now. Operators that cannot move to 1.13.0 yet have no vendor-provided interim fix to apply.



