IBM Langflow Flaw CVE-2026-110186: Update Now
Published October 29, 2026 · Last updated October 29, 2026
The short version: CVE-2026-110186 is a critical-severity security flaw in IBM Langflow. The National Vulnerability Database (NVD) published it on October 29, 2026, and the score it lists is 9.8 out of 10. When FraudMeNot checked on October 29, 2026, CISA had not added CVE-2026-110186 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.
What the official record says about CVE-2026-110186
The record was filed by us.ibm.com. In its own words: "IBM Langflow OSS 1.0.0 through 1.12.8 could allow a remote attacker to execute arbitrary code due to improper control of code generation."
Why Langflow admins should care
Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on us.ibm.com rated CVE-2026-110186 9.8 (Critical) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker does not need an account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping Langflow running is high. Scoring string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Affected Langflow releases
According to the record, these releases are vulnerable:
- 1.0.0 through 1.12.8
The type of bug behind CVE-2026-110186
NVD classifies it using MITRE's Common Weakness Enumeration:
- CWE-94, Improper Control of Generation of Code. MITRE describes this class of bug as follows: "The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. (Roles: Common-Name, Attack-Focused)"
Vendor remediation for CVE-2026-110186
The vendor advisory remediation for operators of Langflow, quoted for this page, is: "IBM's security bulletin, first published October 28, 2026, tells anyone running Langflow OSS 1.0.0 through 1.12.8 to upgrade to Langflow OSS 1.13.0. For a Python install that means running pip install --upgrade "langflow==1.13.0"; for Docker, pull the langflowai/langflow:1.13.0 image and restart while keeping persistent data. Back up the database, the secret key, and uploaded files before you start. If you rely on automatic login, set up password sign-in for the existing account first, as IBM's upgrade instructions describe. IBM lists no interim workaround, so the same bulletin's other Langflow fixes (CVE-2026-93680 authentication bypass and CVE-2026-110193 agentic assistant code execution) arrive with the same upgrade. Until it is done, keep Langflow off the open internet and behind a VPN."
What to do about it
- Update now: IBM's security bulletin, first published October 28, 2026, tells anyone running Langflow OSS 1.0.0 through 1.12.8 to upgrade to Langflow OSS 1.13.0. For a Python install that means running pip install --upgrade "langflow==1.13.0"; for Docker, pull the langflowai/langflow:1.13.0 image and restart while keeping persistent data. Back up the database, the secret key, and uploaded files before you start. If you rely on automatic login, set up password sign-in for the existing account first, as IBM's upgrade instructions describe. IBM lists no interim workaround, so the same bulletin's other Langflow fixes (CVE-2026-93680 authentication bypass and CVE-2026-110193 agentic assistant code execution) arrive with the same upgrade. Until it is done, keep Langflow off the open internet and behind a VPN.
- Who should act: IT teams, managed service providers, and developers who run or ship Langflow. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
- Read the official advisory from IBM (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
- After patching, confirm the new version is actually running and review logs from October 29, 2026 onward for anything unusual.
- Home users: you do not need to buy or download anything because of CVE-2026-110186. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.
CVE-2026-110186 record details from CISA and NVD
- Attack complexity for CVE-2026-110186: low
- CVE-2026-110186 CVSS scope: unchanged
- NVD sub-scores for CVE-2026-110186: exploitability 3.9, impact 5.9.
- Who mapped the weakness type: the address listed on us.ibm.com (Primary)
- References in the NVD record: 1.
Dates to know
- October 29, 2026: NVD publishes CVE-2026-110186.
- October 29, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-110186 is not listed.
- October 29, 2026: most recent NVD update (record status: Undergoing Analysis).
Official references
Links listed in the NVD record (labels in brackets come from NVD):
Sources
General education only, not security advice. Facts checked against the sources above on the date shown.