# CVE-2026-18894: Langflow OSS is affected by multiple vulnerabilities


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-pf68-vvvh-6f8f

## What is CVE-2026-18894?

CVE-2026-18894 is a medium-severity vulnerability in IBM Langflow OSS, published on 29 Oct 2026. 

### Official description

IBM Langflow OSS 1.0.0 through 1.12.4 could allow a remote attacker to trigger pre-existing stored Python component code in a public workflow, executing it under the flow owner's runtime context within the server process. This bypasses the intended trust boundary where public execution paths are restricted to server-trusted component code.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2026-18894 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18894 is a medium-severity vulnerability in IBM Langflow OSS, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-18894 in the wild and no public exploit code.

Affected product: IBM Langflow OSS. 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-18894/ (Markdown: https://insights.sbomify.com/CVE-2026-18894/index.md)
```

## Sources

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

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