CVE-2026-10129: high-severity vulnerability in IBM Langflow OSS
SSRF via HTTP Redirect Following in Langflow API Request Component
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.5epss 0.3%
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
Affected products
IBM · Langflow OSSRelated CVEs — IBM Langflow OSS
In the same product, most dangerous first.
CVE-2026-9198CRITICALUnauthenticated Remote Code Execution via Auto-Login Bypass and Code ValidationEPSS 28.7%KEVCVE-2026-93674CRITICALLangflow OSS is affected by multiple vulnerabilitiesEPSS 14.1%CVE-2026-7873CRITICALCode Injection Vulnerability in Code Validation EndpointEPSS 6.9%CVE-2026-93680CRITICALLangflow OSS is affected by multiple vulnerabilitiesEPSS 3.2%CVE-2026-9103CRITICALUnauthenticated Superuser Token Issuance via Auto-Login EndpointEPSS 3.2%CVE-2026-10134CRITICALUnauthenticated Server-Side RCE via PythonCodeStructuredTool in Public FlowsEPSS 2.3%