Quick answers
- Is CVE-2026-17631 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-17631 being exploited in the wild.
- How severe is CVE-2026-17631?
- Medium severity, with a CVSS score of 5, published 4 September 2026.
- Which products and versions are affected?
- IBM Langflow OSS 1.0.0 through 1.10.2.
- Is there a fix for CVE-2026-17631?
- A patch was published on 2026: Fix available in version 1.10.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-17631 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-17631?
- Check whether you run Apple macOS, IBM Langflow OSS, Langflow or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This is a server-side request forgery (SSRF) vulnerability (CWE-918) caused by missing URL validation in flow components that perform outbound HTTP requests. Multiple components (LM Studio, Home Assistant, DeepSeek, xAI, Glean, HuggingFace Inference API, Ollama, LiteLLM, and Docling Serve) accept user-supplied URLs without applying Langflow's existing SSRF protection utilities. The Docling Serve component additionally bypasses SSRF protection even when LANGFLOW_SSRF_PROTECTION_ENABLED is enabled. An authenticated attacker can reach arbitrary internal or external network destinations through standard authenticated flow execution and component configuration API endpoints, with response content potentially disclosed through component output or error messages. The vulnerability is non-blind SSRF allowing information disclosure. A fix is available in version 1.10.3.
Affected products
- IBM Langflow OSS 1.0.0 through 1.10.2
Timeline
- 2026-08-28: disclosed
- 2026: patched: Fix available in version 1.10.3