CVE-2026-10564: high-severity vulnerability in IBM Langflow OSS
SSRF Vulnerability in Langflow OSS Legacy Components Bypasses Protection
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.2epss 0.4%
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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%