# CVE-2026-101861: Langflow Code Execution via eval() in Component Input Schema

> Authenticated attackers can execute arbitrary code in Langflow by injecting malicious Python objects into component input schemas via unsafe eval usage.

- **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-33p4-w7j3-33mw

## What is CVE-2026-101861?

CVE-2026-101861 is a low-severity code injection vulnerability in langflow-ai langflow, published on 28 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Langflow 1.0.16 before 1.12.0 and 0.0.94 before 1.12.0 contain an unsafe eval() vulnerability in schema.py that allows authenticated attackers to achieve code execution by placing a Python object with a malicious __repr__ method into component input options lists. The eval() sink is triggered when a component is converted into a LangChain tool via ComponentToolkit.get_tools(), including during custom component saves through the API, by interpolating options into a Literal type string that is passed directly to eval() without safe evaluation controls.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code), CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-101861?


## How do I fix CVE-2026-101861?

No fix has been published for CVE-2026-101861 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-101861 being exploited?

There is no known exploitation of CVE-2026-101861 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-101861 and fix it if it is affected.

What it is: CVE-2026-101861 is a low-severity code injection vulnerability in langflow-ai langflow, published on 28 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-101861 in the wild and no public exploit code.

Affected product: langflow-ai langflow. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-101861/ (Markdown: https://insights.sbomify.com/CVE-2026-101861/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-101861
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-101861
- OSV: https://osv.dev/vulnerability/CVE-2026-101861

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-101861/
Summaries are generated and may contain mistakes; the official description above is the record.