Langflow: IBM Langflow OSS 1.0.0 through 1.11.5 An attacker who could submit custom component source code…
Langflow
More for Langflow RSS feed for Langflow
- Severity
- High, CVSS 8.8
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Record
- CVE-2026-76059
- Affects
- Langflow
- Known exploited
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Published
- Record first published by the source
- September 10, 2026
- Source last modified
- September 16, 2026
Description
IBM Langflow OSS 1.0.0 through 1.11.5 An attacker who could submit custom component source code could bypass the static security scanner by crafting an annotated class-body assignment that resolved to a dangerous callable through alias tracking; the resolved value was never checked against the dangerous callable blocklist due to the logic error. If the crafted component reached the runtime execution path, the attacker could cause arbitrary operating system commands to execute on the server in-process, with the privileges of the running service.
Description quoted from the NVD record.
Who is affected
Langflow (also called IBM Langflow OSS) is a tool for building apps that use AI language models. This flaw affects versions 1.0.0 through 1.11.5. It involves the feature that lets users add their own custom components (pieces of program code) to the product. A built-in safety check is meant to block dangerous code in those components, but a mistake in it lets specially written code slip past. Someone who can submit a custom component could then, if that component is run, run any commands they choose on the server running Langflow, with the same access the product has. This flaw is rated High.
What to do
- The person who installed or runs Langflow for your organization should handle this.
- If an IT provider or vendor runs Langflow for you, send them this advisory and ask when the update will be done.
- Find out which version of Langflow you use. Versions 1.0.0 through 1.11.5 are affected by this flaw.
- No fixed version is named for this flaw yet, so check the vendor advisory linked on this page for a fixed release and install it as soon as it is available.
Analysis written from the source record as of September 16, 2026 and reviewed before publishing.