# CVE-2026-9198: IBM Langflow Code Injection

> Unauthenticated attackers can achieve remote code execution by chaining auto-login token generation with code validation endpoints in Langflow OSS.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 4 Aug 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-5wm9-vgmg-cjv6

## What is CVE-2026-9198?

CVE-2026-9198 is a critical code injection vulnerability in Langflow Langflow, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM Langflow OSS 1.0.0 through 1.10.0 allows unauthenticated attackers to chain /api/v1/auto_login (mints SUPERUSER tokens to any network caller) with /api/v1/validate/code (executes user code via exec()) to achieve full RCE on default Langflow deployments

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

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

It affects 1 product.


Products: Langflow Langflow.

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

No fix has been published for CVE-2026-9198 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 7 Aug 2026.

## Is CVE-2026-9198 being exploited?

Yes. Attackers have exploited CVE-2026-9198 in the wild since at least 4 Aug 2026.

Public exploit code:

- IBM Langflow Unauthenticated RCE via Auto-Login Bypass (github_poc): https://github.com/0xgh057r3c0n/CVE-2026-9198
- https://github.com/0xdak/CVE-2026-9198_exploit (github_poc): https://github.com/0xdak/CVE-2026-9198_exploit
- Proof of concept exploit code for CVE-2026-9198 (github_poc): https://github.com/rmhowe425/PoC-CVE-2026-9198
- Langflow AI auto_login RCE (metasploit)
- Proof of Concept for CVE-2026-9198 - IBM Langflow Unauthenticated RCE via Auto-Login Bypass (github_poc): https://github.com/ywh-jfellus/CVE-2026-9198
- https://github.com/Procjevt/CVE-2026-9198 (github_poc): https://github.com/Procjevt/CVE-2026-9198

## Other vulnerabilities in Langflow Langflow

- [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)
- [CVE-2026-55255](https://insights.sbomify.com/CVE-2026-55255/): Langflow Authorization Bypass Through User-Controlled Key (high 8.4, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9198 is a critical code injection vulnerability in Langflow Langflow, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-9198 in the wild since at least 4 Aug 2026.

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

## Sources

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

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