Is CVE-2026-101861 exploited in the wild?

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

How severe is CVE-2026-101861?

Medium severity, with a CVSS score of 4.1, published 28 September 2026.

Which products and versions are affected?

Langflow 1.0.16 to 1.11.6; Langflow-Base 0.0.94 to 1.11.6; Langflow Lfx before 1.12.0.

Is there a fix for CVE-2026-101861?

A patch was published on 2026-09-28: Fix released in versions langflow 1.12.0, langflow-base 1.12.0, lfx 1.12.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-101861 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-101861?

Check whether you run Langflow, Langflow-Base or Langflow Lfx 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-101861: Langflow unsafe eval() in schema.py code execution

CVE-2026-101861 · Severity: medium · CVSS 4.1 · Published 2026-09-28

Langflow is a platform for building AI applications with components and flows. An unsafe eval() vulnerability in schema.py allows authenticated attackers to execute arbitrary Python code when converting components into LangChain tools, including when saving custom components. However, exploiting this requires the attacker to already have component authoring privileges, which grants equivalent code execution capabilities directly.

Technologies: Langflow, Langflow-Base, Langflow Lfx. Vendors: Langflow.

Quick answers

Is CVE-2026-101861 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-101861 being exploited in the wild.
How severe is CVE-2026-101861?: Medium severity, with a CVSS score of 4.1, published 28 September 2026.
Which products and versions are affected?: Langflow 1.0.16 to 1.11.6; Langflow-Base 0.0.94 to 1.11.6; Langflow Lfx before 1.12.0.
Is there a fix for CVE-2026-101861?: A patch was published on 2026-09-28: Fix released in versions langflow 1.12.0, langflow-base 1.12.0, lfx 1.12.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-101861 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-101861?: Check whether you run Langflow, Langflow-Base or Langflow Lfx 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 exists in create_input_schema() and create_input_schema_from_dict() functions in schema.py, which build typing.Literal types by interpolating component options into a string passed directly to eval(). The sink is triggered via ComponentToolkit.get_tools() when components are converted to tools, including during custom component saves (POST /api/v1/custom_component) and tool-mode component builds. Exploitation requires embedding a Python object with a malicious __repr__ method in component options; in practice this requires component authoring capability, which already permits arbitrary code execution. The vulnerability was fixed in version 1.12.0 by replacing eval() with safe literal construction.

Affected products

Langflow langflow 1.0.16 to 1.11.6
Langflow langflow-base 0.0.94 to 1.11.6
Langflow lfx before 1.12.0

Timeline

2026-09-28: disclosed: GHSA-33p4-w7j3-33mw published
2026-09-28: patched: Fix released in versions langflow 1.12.0, langflow-base 1.12.0, lfx 1.12.0

References

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