Security notice
Run your own Langflow server? Two flaws rated 9.8 need no account. Upgrade to 1.13.0.
Langflow is an open-source tool for building AI agents and workflows. On October 28, 2026, IBM, which issues the security bulletins for Langflow, listed two flaws in it that it rates 9.8 out of 10, the critical level, and that need no account: CVE-2026-93680, which IBM describes as a bypass of authentication, and CVE-2026-110186, which IBM describes as a way to run arbitrary code on the server. They affect Langflow 1.0.0 through 1.12.8, including 1.12.8, which came out on October 22. Version 1.13.0, released the same day, is the fix, and IBM lists no workaround. CISA does not list either flaw as exploited and we found no report of attacks. A public scanning module that cites CVE-2026-93680 exists, and CISA's list already holds six earlier Langflow flaws that were exploited. This is not a website or store flaw. It matters if you or an IT provider run your own Langflow server, especially one that can be reached from the internet, because whoever controls that server controls what its flows can reach. Back it up, then upgrade to 1.13.0 today.
What happened
- The flaws. IBM's bulletin, "Langflow OSS is affected by multiple vulnerabilities," was first published on October 28, 2026 and updated on October 29. It lists two critical flaws that need no account. For CVE-2026-93680, IBM says a remote attacker could bypass security restrictions "due to improper authentication." For CVE-2026-110186, IBM says a remote attacker could execute arbitrary code "due to improper control of code generation." Running code on a server means a stranger runs their own commands on it. IBM's summary also names "unauthenticated remote code execution exploitable through model context protocol tool enumeration," which relates to how Langflow offers its flows as tools to AI apps, but it does not say which CVE that is. We are leaving out the technical details. (IBM bulletin, CVE-2026-93680 record, CVE-2026-110186 record, The Hacker News)
- How serious. IBM scores both CVSS 9.8, which is 9.8 out of 10 and critical: reachable over the network, low complexity, no account and no user action needed. The CISA assessment attached to both CVE records, dated October 30, says exploitation is "none," that an attack can be automated, and that the technical impact is "total." (IBM bulletin, CVE-2026-93680 record, CVE-2026-110186 record)
- Two more flaws in the same bulletin. CVE-2026-110193 (8.8) needs a low-privileged account and involves Langflow's Agentic Assistant, and IBM says it could run operating system commands on the server. CVE-2026-110192 (6.5) lets a signed-in attacker obtain sensitive information, because of insufficiently protected credentials. The same upgrade covers them. (IBM bulletin)
- Affected and fixed versions. Langflow 1.0.0 through 1.12.8. Version 1.12.8 is not safe: GitHub shows it was released on October 22 at 1:08 PM ET, and 1.13.0 followed the same day at 5:20 PM ET. IBM says to upgrade to 1.13.0, and PyPI lists 1.13.0 as the newest stable release. (IBM bulletin, Langflow 1.13.0 release, PyPI)
- The release notes do not name the flaws. The Langflow 1.13.0 release notes and Langflow's own GitHub security advisories do not mention these CVE numbers, so we rely on IBM for the statement that 1.13.0 fixes them. (Langflow 1.13.0 release, IBM bulletin)
- No workaround. IBM's bulletin lists workarounds and mitigations as "None." Upgrading is the only fix IBM gives. (IBM bulletin)
- Automatic login. Langflow has a setting called automatic login that signs people in without a password. Langflow's own code describes it as something that "bypasses authentication and should only be used in development environments." In the Langflow 1.12.8 code it is on by default for the Python package, and in the Langflow 1.13.0 code it is off by default. Langflow's documentation says that as of 1.11.x its official Docker images have it off. IBM's summary lists "an incomplete remediation of an auto-login security control" among the issues, but the bulletin does not say whether a server with automatic login turned off is safe. Do not rely on that setting. (Langflow 1.12.8 code, Langflow 1.13.0 code, Langflow installation guide, Langflow Docker upgrade guide, IBM bulletin)
- No attacks reported. CISA KEV does not list either CVE in its version dated October 30, 2026, which we checked directly on November 2, and The Hacker News says the same. We found no report that anyone is attacking these flaws. That does not mean they have not been. A public scanning module that cites CVE-2026-93680 exists; The Hacker News says it does not run code on the server. We have not tested it and do not link it. The same CISA catalog lists six earlier Langflow flaws as exploited, the latest added on August 4, 2026. (CISA KEV, The Hacker News)
- Other Langflow flaws. The Hacker News reports that on October 29, IBM also published records for 29 other Langflow flaws, with fixes in versions 1.12.4 and 1.12.5. One of them, CVE-2026-104339 record, is also rated 9.8 and needs no account, and its record lists versions 1.0.0 through 1.12.3. None of the records we read lists 1.13.0 as affected. (The Hacker News, CVE-2026-104339 record)
Who should worry
This is not a flaw in websites or online stores. It is in a tool that teams run on their own servers to build AI agents and workflows. It matters for your business if an agency, developer or IT person runs Langflow, especially if the server can be reached from the internet, because it usually holds the keys and passwords its flows use to reach AI services, databases and other tools. IBM's bulletin lists exposure of API credentials among the issues. If you are not sure, ask. Ask about this if any of these are true:
- You or your IT provider run your own Langflow server, installed with pip, in Docker or from source.
- The server runs Langflow 1.12.8 or older, or nobody knows which version it runs.
- The Langflow server can be reached from the internet, or from many people or networks.
- An agency or developer built AI chat, agents or automations for your business and you do not know where they run.
- You run an agency or host and look after Langflow servers for clients.
If a provider hosts Langflow for you, ask whether it runs 1.13.0 or later. We found no IBM statement about hosted services. We also found no statement about Langflow Desktop. The bulletin covers "Langflow OSS" on Windows, Linux and Mac OS. If nobody you work with uses Langflow, this notice does not apply to you.
What to do now
These steps are for whoever runs the Langflow server. If that is not you, send them the message below.
- Find out if you run it, and which version. For a pip install,
pip show langflowprints the version. If it is 1.12.8 or older, it is affected. - Back up first. IBM says to back up the database, the secret key and the uploaded files before upgrading. (IBM bulletin)
- If it signs in automatically, prepare for password sign-in. Langflow 1.13 turns automatic login off by default. IBM and Langflow say to prepare the existing account for password sign-in before you upgrade. If you upgrade without doing so you may be unable to sign in. If that happens, follow Langflow's recovery steps, and do not delete or reinstall Langflow to get back in, because Langflow warns that can permanently remove your flows. (IBM bulletin, Langflow installation guide, Langflow Docker upgrade guide)
- Upgrade to 1.13.0. IBM gives
pip install --upgrade "langflow==1.13.0"for the Python package. For Docker, use the imagelangflowai/langflow:1.13.0and keep the deployment's persistent data. Then check that the version is 1.13.0 and that you can sign in. (IBM bulletin) - If you cannot upgrade today, IBM offers no workaround. As a general precaution, not IBM's advice, ask your admin whether the server can be taken off the internet or limited to the people and networks that need it until you upgrade.
- Check for a break-in. No signs of attack have been published, so there is nothing specific to look for. As a general check, especially if the server was on 1.12.8 or older and reachable from the internet, ask your admin to review who has accounts, which flows were added or changed recently, and what keys and passwords are stored in Langflow. If there is any sign of a problem, or you cannot rule it out, replace those keys and passwords.
What to send your IT provider or host
Langflow 1.0.0 through 1.12.8 has two critical flaws that need no account, CVE-2026-93680 (an authentication bypass) and CVE-2026-110186 (arbitrary code execution), both rated 9.8 by IBM, which published its bulletin on October 28, 2026. IBM lists no workaround and says to upgrade to 1.13.0. CISA does not list them as exploited. Please tell us whether we run any Langflow server, which version it is, and whether it can be reached from the internet. If it is 1.12.8 or older, please back up the database, secret key and uploaded files, prepare any automatic-login account for password sign-in, and upgrade to 1.13.0 today. Please then check for unexpected accounts or flows, replace any keys or passwords you cannot be sure are safe, and tell us what you find. Sources: IBM's bulletin, the CVE records, Langflow's installation guide.
Common questions
Is my website affected?
Not directly. The flaws are in Langflow, a tool for building AI agents and workflows, not in website or store software. They matter if your business runs its own Langflow server, because whoever controls that server controls what its flows can reach.
Can EverThread tell me if I am affected?
No. EverThread does not test for this. We check your website from the outside, the way a browser sees it. We cannot see whether you run Langflow, which version it is on or whether it can be reached from the internet. Whoever manages the server can check. Our free scan does look at your home page for other common problems, such as an expired padlock certificate, missing browser safety settings and files that should not be public.
Is it being exploited?
We found no report that it is. CISA does not list either flaw as exploited, and its own assessment says exploitation is "none." A public scanning module for CVE-2026-93680 exists, and CISA lists six earlier Langflow flaws as exploited, so do not wait. (CISA KEV, CVE-2026-93680 record, CVE-2026-110186 record, The Hacker News)
I am on 1.12.8, the latest 1.12 release. Am I safe?
No. IBM lists 1.12.8 as affected. You need 1.13.0. (IBM bulletin)
Does turning off automatic login protect me?
We do not know. IBM's bulletin does not say whether a server with automatic login off is safe, and it lists no workaround. Upgrade to 1.13.0. (IBM bulletin)
Where can I follow official updates?
The IBM bulletin and the Langflow 1.13.0 release page. All current notices are on our notices page.
Security alerts by email
Hear about the next one first.
When a flaw puts websites at risk, we send one plain-English email: what happened, who it affects and what to do. It's free, whether or not you use EverThread.
Sources
- IBM: Security Bulletin: Langflow OSS is affected by multiple vulnerabilities, first published October 28, 2026, updated October 29, 2026, checked November 2, 2026
- CVE Program: CVE-2026-93680 and CVE-2026-110186, published October 29, 2026 by IBM, with CISA's assessment dated October 30, 2026, checked November 2, 2026
- The Hacker News: Critical Langflow Flaws Could Let Unauthenticated Attackers Run Code on Servers, Swati Khandelwal, November 2, 2026, checked November 2, 2026
- Langflow: 1.13.0 release notes on GitHub, October 22, 2026, checked November 2, 2026
- Langflow: automatic login setting in the code of version 1.12.8 and version 1.13.0, checked November 2, 2026
- Langflow: Install Langflow and Upgrade the Langflow Docker image, documentation, checked November 2, 2026
- PyPI: langflow, release list, checked November 2, 2026
- CVE Program: CVE-2026-104339, published October 29, 2026 by IBM, checked November 2, 2026
- CISA: Known Exploited Vulnerabilities Catalog, catalog version dated October 30, 2026, checked November 2, 2026