CVE-2026-10129

HighCVSS 8.5

Published: 30/06/2026(UTC)Updated: 02/07/2026(UTC)Translated: 03/07/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.20%

9th percentile — higher than 9% of all known CVEs

Summary

IBM Langflow OSS versions 1.0.0 through 1.9.3 contain 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.

Risk Assessment

The risk for the organization includes potential disclosure of sensitive information such as credentials, tokens, internal API responses, and administrative panel data by accessing internal HTTP services, localhost endpoints, cloud metadata services, and private network resources.

Recommendation

It is recommended to immediately upgrade IBM Langflow OSS to version 1.9.4 or later, which includes a fix for this vulnerability. As a temporary mitigation, disable the follow_redirects parameter in the API Request configuration or restrict its use to trusted users only.

Original NVD description (English source)

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.