Skip to content

This latest round of security patches fix four vulnerabilities

www.ibm.com • November 3, 2026

Langflow OSS is affected by multiple vulnerabilities that could allow a remote attacker to bypass authentication controls, execute arbitrary code, expose application programming interface (API) credentials, or disclose information through vulnerable dependencies. Issues include an incomplete remediation of an auto-login security control, agentic code execution via a third-party library, operator-injected API key exposure reachable without intended authorization, and unauthenticated remote code execution exploitable through model context protocol tool enumeration. Additionally, several open-source dependencies included in the product contain known vulnerabilities.

Vulnerability Details

CVEID: CVE-2026-93680 DESCRIPTION: Langflow OSS could allow a remote attacker to bypass security restrictions due to improper authentication. CWE: CWE-287: Improper Authentication CVSS Source: IBM CVSS Base score: 9.8 CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) CVEID: CVE-2026-110193 DESCRIPTION: Langflow OSS could allow a remote attacker with a low-privileged authenticated account to cause the Agentic Assistant to generate or submit component code using these unblocked patterns, resulting in arbitrary operating system command execution on the server. CWE: CWE-94: Improper Control of Generation of Code ('Code Injection') CVSS Source: IBM CVSS Base score: 8.8 CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) CVEID: CVE-2026-110186 DESCRIPTION: Langflow OSS could allow a remote attacker to execute arbitrary code due to improper control of code generation. CWE: CWE-94: Improper Control of Generation of Code ('Code Injection') CVSS Source: IBM CVSS Base score: 9.8 CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) CVEID: CVE-2026-84363 DESCRIPTION: Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.13.5, Hono's query helpers treat a question mark after a literal hash fragment as the start of a query string, so the application can read request parameters that browsers, new URL(), reverse proxies, filtering rules, parameter allow and deny lists, access logging, request validation, and other middleware do not observe. The Cache Middleware removes the fragment when building its cache key, allowing a response influenced by parameters inside the fragment to be stored under a key that omits those parameters and later served to other users. This can bypass filtering and auditing, poison cached responses, and enable stored cross-site scripting when an affected parameter is reflected into cached HTML without escaping. Exploitation requires a runtime and intermediary path that passes a literal hash character through to the request URL; Cloudflare Workers and intermediaries that strip fragments are not affected. This issue is fixed in version 4.13.5. CWE: CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') CVSS Source: [email protected] CVSS Base score: 5.9 CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N) CVEID: CVE-2026-84364 DESCRIPTION: Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.13.5, when parseBody() expands dot-separated form field names into nested objects with dot-notation parsing enabled, it does not limit the nesting depth or the total number of intermediate objects created. Empty segments are preserved, so one deeply dotted field name can encode one nesting level per byte, while a large number of shallowly dotted fields can create the same amplification across a request. A request body within a normal size limit can therefore allocate an object graph far larger than the request after the body has already been accepted. An unauthenticated attacker who can reach an affected endpoint can send concurrent requests that exhaust the JavaScript heap, terminate the server process, and leave the service unavailable until restart. Dot-notation parsing is not enabled by default, and applications using the default behavior are not affected. This issue is fixed in version 4.13.5. CWE: CWE-400: Uncontrolled Resource Consumption CVSS Source: [email protected] CVSS Base score: 5.3 CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) CVEID: CVE-2026-84365 DESCRIPTION: Hono is a Web application framework that provides support for any JavaScript runtime. From 4.12.12 until 4.13.5, the fix released for CVE-2026-39408 does not cover every traversal sequence, and toSSG() can still write files outside the configured output directory when a route parameter contains consecutive parent-directory segments. Static site generation builds each output path from the route path and values supplied through ssgParams, then verifies that the result stays inside the output directory using the same normalization routine that built the path. That routine does not fully collapse runs of consecutive parent-directory segments, allowing a path that the check accepts to resolve outside the output directory, and the check also treats output directories that differ in how they are rooted as equivalent. This arises when an application generates a static site from route parameter values it does not fully control, such as slugs from a CMS, API, or user submission. An untrusted ssgParams value can create or overwrite files elsewhere in the build environment and alter generated artifacts or deployment output. The vulnerability affects build-time static site generation only; request-time routing and applications with entirely developer-controlled ssgParams values are not affected. This issue is fixed in version 4.13.5. CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') CVSS Source: [email protected] CVSS Base score: 6.5 CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N) CVEID: CVE-2026-110192 DESCRIPTION: Langflow OSS could allow a remote authenticated attacker to obtain sensitive information due to insufficiently protected credentials. CWE: CWE-522: Insufficiently Protected Credentials CVSS Source: IBM CVSS Base score: 6.5 CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N)

Affected Products and Versions

Affected Product(s) Version(s) Langflow OSS 1.0.0 - 1.12.8

IBM strongly recommends addressing these vulnerabilities now by upgrading Langflow OSS installations running versions 1.0.0 - 1.12.8 to Langflow OSS 1.13.0. Review the Langflow OSS 1.13.0 release notes and follow the installation instructions for your deployment: Python package: install Langflow 1.13.0 from PyPI with pip install --upgrade "langflow==1.13.0" , following the installation instructions . Docker: use langflowai/langflow:1.13.0 and follow the Docker upgrade instructions to pull the image and restart the deployment while preserving its persistent data. Before upgrading, back up the database, secret key, and uploaded files. If the deployment uses automatic login, prepare the existing account for password sign-in as described in the installation and Docker upgrade instructions. These preparation steps accompany the product upgrade; no separate interim workaround is provided.

IBM strongly recommends addressing these vulnerabilities now by upgrading Langflow OSS installations running versions 1.0.0 - 1.12.8 to Langflow OSS 1.13.0.

Review the Langflow OSS 1.13.0 release notes and follow the installation instructions for your deployment:

Python package: install Langflow 1.13.0 from PyPI with pip install --upgrade "langflow==1.13.0" , following the installation instructions .

Docker: use langflowai/langflow:1.13.0 and follow the Docker upgrade instructions to pull the image and restart the deployment while preserving its persistent data.

Before upgrading, back up the database, secret key, and uploaded files. If the deployment uses automatic login, prepare the existing account for password sign-in as described in the installation and Docker upgrade instructions. These preparation steps accompany the product upgrade; no separate interim workaround is provided.

Workarounds and Mitigations

Get Notified Future Security Bulletins

Complete CVSS v3 Guide On-line Calculator v3

29 Oct 2026: Updated summary, clarified fixed-version remediation and installation instructions, and corrected taxonomy version formatting.28 Oct 2026: Initial Publication

*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.

According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES ""AS IS"" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. In addition to other efforts to address potential vulnerabilities, IBM periodically updates the record of components contained in our product offerings. As part of that effort, if IBM identifies previously unidentified packages in a product/service inventory, we address relevant vulnerabilities regardless of CVE date. Inclusion of an older CVEID does not demonstrate that the referenced product has been used by IBM since that date, nor that IBM was aware of a vulnerability as of that date. We are making clients aware of relevant vulnerabilities as we become aware of them. "Affected Products and Versions" referenced in IBM Security Bulletins are intended to be only products and versions that are supported by IBM and have not passed their end-of-support or warranty date. Thus, failure to reference unsupported or extended-support products and versions in this Security Bulletin does not constitute a determination by IBM that they are unaffected by the vulnerability. Reference to one or more unsupported versions in this Security Bulletin shall not create an obligation for IBM to provide fixes for any unsupported or extended-support products or versions.

According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES ""AS IS"" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. In addition to other efforts to address potential vulnerabilities, IBM periodically updates the record of components contained in our product offerings. As part of that effort, if IBM identifies previously unidentified packages in a product/service inventory, we address relevant vulnerabilities regardless of CVE date. Inclusion of an older CVEID does not demonstrate that the referenced product has been used by IBM since that date, nor that IBM was aware of a vulnerability as of that date. We are making clients aware of relevant vulnerabilities as we become aware of them. "Affected Products and Versions" referenced in IBM Security Bulletins are intended to be only products and versions that are supported by IBM and have not passed their end-of-support or warranty date. Thus, failure to reference unsupported or extended-support products and versions in this Security Bulletin does not constitute a determination by IBM that they are unaffected by the vulnerability. Reference to one or more unsupported versions in this Security Bulletin shall not create an obligation for IBM to provide fixes for any unsupported or extended-support products or versions.

Was this topic helpful?

Modified date: 29 October 2026

Initial Publish date: 28 October 2026