# CVE-2026-19295: Code injection in Langflow OSS

> Authenticated attackers can execute arbitrary OS commands by bypassing custom component restrictions, leading to privilege escalation.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-74fg-mx2g-3cx8

## What is CVE-2026-19295?

CVE-2026-19295 is a critical code injection vulnerability in Langflow Langflow, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Langflow OSS 1.0.0 through 1.11.1 allows an authenticated attacker to execute arbitrary operating system commands in the server process by saving a flow with a crafted type field value and triggering a build of a wrapper flow that references it. This allowed privilege escalation from "authenticated flow user" to arbitrary OS-level command execution under the server process identity, bypassing the LANGFLOW_ALLOW_CUSTOM_COMPONENTS=false policy control.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code)

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

It affects 1 product.


Products: Langflow Langflow.

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

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

## Is CVE-2026-19295 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19295 exists.

Public exploit code:

- Langflow AI authenticated RCE (metasploit)
- Proof of concept exploit code for CVE-2026-19295 (github_poc): https://github.com/rmhowe425/POC-CVE-2026-19295

## Other vulnerabilities in Langflow Langflow

- [CVE-2026-9198](https://insights.sbomify.com/CVE-2026-9198/): IBM Langflow Code Injection (critical 9.8, exploited in the wild)
- [CVE-2026-0770](https://insights.sbomify.com/CVE-2026-0770/): Langflow Inclusion of Functionality from Untrusted Control Sphere (critical 9.8, exploited in the wild)
- [CVE-2025-3248](https://insights.sbomify.com/CVE-2025-3248/): Langflow Missing Authentication (critical 9.8, exploited in the wild)
- [CVE-2025-34291](https://insights.sbomify.com/CVE-2025-34291/): Langflow Origin Validation Error (critical 9.4, exploited in the wild)
- [CVE-2026-33017](https://insights.sbomify.com/CVE-2026-33017/): Langflow Code Injection (critical 9.3, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19295 is a critical code injection vulnerability in Langflow Langflow, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19295 exists.

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

## Sources

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

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