# CVE-2026-9130: Langflow OSS is affected by arbitrary code execution in custom component validation and trusted code enforcement

> Authenticated users can access other users' chat history in multi-user Langflow deployments due to missing ownership validation in memory components.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **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:** 5 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-vph6-jp7f-x3cx

## What is CVE-2026-9130?

CVE-2026-9130 is a high-severity missing authorization vulnerability in Langflow Langflow, published on 5 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.10.3 contain an authorization bypass vulnerability in the MemoryComponent that allows authenticated users to access chat history of other users via session_id collision. The MemoryComponent.retrieve_messages and store_message methods filter on session_id without validating flow_id or user_id ownership, enabling cross-user information disclosure through multiple authenticated API endpoints including /api/v1/run/*, /api/v1/responses, and /api/v2/workflow/*. This vulnerability only affects multi-user deployments with LANGFLOW_AUTO_LOGIN=False.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Langflow Langflow.

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

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

## Is CVE-2026-9130 being exploited?

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

## 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-9130 and fix it if it is affected.

What it is: CVE-2026-9130 is a high-severity missing authorization vulnerability in Langflow Langflow, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9130 in the wild and no public exploit code.

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

## Sources

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

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