Langflow: IBM Langflow OSS 1.0.0 through 1.10.3, and 1.0.0 through 1.10.3 contains a Server-Side Request…
Langflow
More for Langflow RSS feed for Langflow
- Severity
- High, CVSS 7.1
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
- Record
- CVE-2026-9081
- Affects
- Langflow
- Known exploited
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Published
- Record first published by the source
- August 5, 2026
- Source last modified
- October 24, 2026
Description
IBM Langflow OSS 1.0.0 through 1.10.3, and 1.0.0 through 1.10.3 contains a Server-Side Request Forgery (SSRF) vulnerability in the validate_model_provider_key() function for the Ollama provider. The function accepts a user-supplied OLLAMA_BASE_URL parameter and passes it directly to requests.get() without validation, scheme/host allowlisting, or filtering of private IP ranges (loopback, RFC1918, link-local addresses).
Description quoted from the NVD record.
Who is affected
This flaw affects Langflow (also called IBM Langflow OSS), a tool for building apps that use AI language models. It affects versions 1.0.0 through 1.10.3. The problem is in the part of Langflow that checks the connection settings for Ollama, a way of running AI models. That part accepts a web address supplied by a user and contacts it without any checks. An attacker could use this to make your Langflow server send web requests to places they choose, including computers and services on your own internal network. This flaw is rated High.
What to do
- Find out who runs Langflow for your organization. This could be the person who installed it, or an IT provider or vendor that manages it. That person or company should act on this advisory.
- Ask them which version of Langflow is installed. Versions 1.0.0 through 1.10.3 are affected.
- No fixed version is named for this flaw yet. The person who runs Langflow should check the vendor advisory linked on this page for a fixed release and install it as soon as one is available.
- If an IT provider or vendor runs Langflow for you, send them this advisory and ask when the update will be done.
Analysis written from the source record as of October 24, 2026 and reviewed before publishing.