CVE-2026-10129: IBM Langflow OSS 1.0.0 through 1.9.3 contains a Server-Side Request Forgery (SSRF) protection bypass vulnerabi

Routine

HIGH 8.5UPGRADE

CVE-2026-10129 is a high-severity flaw (CVSS 8.5) affecting langflow. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 76%)
CISA exploited list	No
Weakness	CWE-918
Published	2026-06-30
Last modified	2026-10-25

Publisher (CNA): IBM Corporation · Vendor: langflow

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-30 20:17 UTCPublished CVE record published
2026-10-25 21:10 UTCUpdated Record last modified

langflow langflow UPGRADE

Affected: >= 1.0.0 and <= 1.9.3

Fixed in: newer than 1.9.3

Safe to downgrade to: a release before 1.0.0

1. Check installed version

apt-cache policy langflow || rpm -q langflow || langflow --version

2. UPGRADE to newer than 1.9.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade langflow

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade langflow

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.0.0 (Debian / Ubuntu)

apt-cache madison langflow sudo apt install langflow=<VERSION_BEFORE_1.0.0> sudo apt-mark hold langflow

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list langflow sudo dnf downgrade langflow-<VERSION_BEFORE_1.0.0> sudo dnf versionlock add langflow

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-10129?

langflow: upgrade to newer than 1.9.3. Exact commands for each OS are on this page.

Is CVE-2026-10129 being exploited?

CVE-2026-10129 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-10129 affect?

CVE-2026-10129 affects langflow. Severity is high (CVSS 8.5). 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 protecti

How urgent is CVE-2026-10129?

Priority 36/100. High severity

Related CVEs

CVE-2026-7528 HIGH 7.1 UPGRADE IBM Langflow OSS 1.0.0 through 1.9.0 could allow a denial of service due to uncontrolled resource consumption.
CVE-2026-5022 MEDIUM 5.3 MITIGATE The '/api/v1/files/images/{flow_id}/{file_name}' endpoint does not enforce any authentication or authorization
CVE-2026-55255 HIGH 8.4 EXPLOITED UPGRADE Langflow Authorization Bypass Through User-Controlled Key Vulnerability
CVE-2026-55450 CRITICAL 9.3 UPGRADE Langflow is a tool for building and deploying AI-powered agents and workflows
CVE-2026-10561 CRITICAL 10.0 UPGRADE IBM Langflow OSS 1.0.0 through 1.9.3 has an vulnerability due to an improper isolation of Python execution com

References

← Back to latest CVEs