# CVE-2026-10129: SSRF via HTTP Redirect Following in Langflow API Request Component

> Authenticated attackers can bypass SSRF protections in Langflow to access internal services and sensitive data via redirect following.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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:** 30 Jun 2026
- **Updated:** 1 Jul 2026
- **Also known as:** GHSA-33xg-qw74-fhr3

## What is CVE-2026-10129?

CVE-2026-10129 is a high-severity server-side request forgery vulnerability in Langflow Langflow, published on 30 Jun 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.9.3 contains a Server-Side Request Forgery (SSRF) protection bypass vulnerability in the API Request component. An authenticated attacker with low-level privileges (flow author role) can bypass SSRF protections by enabling the follow_redirects parameter and supplying a public URL that redirects to internal/localhost addresses. The vulnerability exists because the application validates only the initial URL but does not re-validate redirect destinations. This allows attackers to access internal HTTP services, localhost endpoints, cloud metadata services, and private network resources that should be unreachable when SSRF protection is enabled. Successful exploitation can lead to disclosure of sensitive information including credentials, tokens, internal API responses, and administrative panel data.

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

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

It affects 1 product.


Products: Langflow Langflow.

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

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

## Is CVE-2026-10129 being exploited?

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

What it is: CVE-2026-10129 is a high-severity server-side request forgery vulnerability in Langflow Langflow, published on 30 Jun 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-10129 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-10129/ (Markdown: https://insights.sbomify.com/CVE-2026-10129/index.md)
```

## Sources

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

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