Is CVE-2026-79724 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-79724 being exploited in the wild.

How severe is CVE-2026-79724?

Critical severity, with a CVSS score of 9.8, published 10 September 2026.

Which products and versions are affected?

IBM Langflow OSS 1.0.0 through 1.11.5.

Is there a fix for CVE-2026-79724?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-79724 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-79724?

Check whether you run IBM Langflow OSS or Langflow at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-79724: IBM Langflow OS command injection via improper neutralization

CVE-2026-79724 · Severity: critical · CVSS 9.8 · Published 2026-09-10

IBM Langflow is a low-code platform for building AI applications that allows developers to create and execute data pipelines and AI workflows. The application fails to properly validate and sanitize OS command inputs, allowing remote attackers to execute arbitrary commands on the server with full system privileges. Successful exploitation could lead to complete server compromise, theft of sensitive data and credentials, unauthorized file modifications, and lateral movement to other systems.

Technologies: IBM Langflow OSS, Langflow. Vendors: IBM, Langflow.

Quick answers

Is CVE-2026-79724 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-79724 being exploited in the wild.
How severe is CVE-2026-79724?: Critical severity, with a CVSS score of 9.8, published 10 September 2026.
Which products and versions are affected?: IBM Langflow OSS 1.0.0 through 1.11.5.
Is there a fix for CVE-2026-79724?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-79724 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-79724?: Check whether you run IBM Langflow OSS or Langflow at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability stems from improper neutralization of special elements used in OS commands (CWE-78), combined with multiple incomplete code security controls and missing execution guards throughout the Langflow codebase. The attack vectors include: incomplete denylist in the agentic assistant code scanner that omits process-spawning primitives; logic errors in class-body assignment safety checks; unsanitized return-type annotation source passed directly to eval(); deprecated flow vertices endpoint accepting attacker-supplied flow data without owner-only validation; insufficient MCP stdio validation (particularly on Windows with alternate cmd.exe switches); missing OPENSSL_CONF environment variable blocklist allowing OpenSSL engine loading; and MCP Tools components bypassing all code-execution restrictions when invoked through flows. A remote unauthenticated attacker can achieve arbitrary OS command execution via multiple attack paths with no user interaction required. Patches addressing these issues are available from IBM.

Affected products

IBM Langflow OSS 1.0.0 through 1.11.5

Timeline

2026-09-10: disclosed

References

https://www.ibm.com/support/pages/node/7286666

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.