# CVE-2026-10564: SSRF Vulnerability in Langflow OSS Legacy Components Bypasses Protection

> Authenticated attackers can exploit SSRF in legacy components to access internal resources and cloud metadata, potentially stealing credentials.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2026
- **Updated:** 1 Jul 2026
- **Also known as:** GHSA-rqjv-px3w-v3w6

## What is CVE-2026-10564?

CVE-2026-10564 is a high-severity server-side request forgery vulnerability in Langflow Langflow, published on 30 Jun 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.9.6 contains a Server-Side Request Forgery (SSRF). The legacy RSSReaderComponent in rss.py and SearXNG component in searxng.py make unvalidated HTTP requests to user-controlled URLs, bypassing SSRF protections introduced in version 1.9.3. An authenticated attacker can exploit this to access internal resources including cloud metadata services (AWS/Azure/GCP IMDS), potentially exfiltrating IAM credentials and enumerating internal networks. The vulnerability can also be triggered through prompt injection in agentic workflows due to tool_mode=True exposure.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Langflow Langflow.

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

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

## Is CVE-2026-10564 being exploited?

There is no known exploitation of CVE-2026-10564 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-10564 and fix it if it is affected.

What it is: CVE-2026-10564 is a high-severity server-side request forgery vulnerability in Langflow Langflow, published on 30 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10564 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-10564/ (Markdown: https://insights.sbomify.com/CVE-2026-10564/index.md)
```

## Sources

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

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