GHSA-j8f7-x8jm-wmm4: Langflow SSRF Vulnerability

MODERATE
CWE-918
Published
Advisory Summary

GHSA-j8f7-x8jm-wmm4 is a MODERATE ssrf vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting Langflow libraries in the PyPI ecosystem. The issue involves ssrf in url-taking components (protection disabled by default / warn-only, not applied to rss, searxng, web search, home assistant, glean, docling). Remediation is available by upgrading affected packages to version 1.10.3, 0.10.3, 0.1.2.

GHSA-j8f7-x8jm-wmm4 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-j8f7-x8jm-wmm4
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product Langflow
Package Ecosystem PyPI
Published Date
Last Updated

How to Fix GHSA-j8f7-x8jm-wmm4

To remediate this vulnerability, upgrade all affected Langflow dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

langflow fixed: 1.10.3
pip install langflow>=1.10.3
langflow-base fixed: 0.10.3
pip install langflow-base>=0.10.3
lfx fixed: 1.10.3
pip install lfx>=1.10.3
lfx-docling fixed: 0.1.2
pip install lfx-docling>=0.1.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show langflow

How to Check if You Are Affected

To determine whether your Python environment is affected by GHSA-j8f7-x8jm-wmm4, inspect your installed packages using pip:

pip show langflow

Analyze the terminal output to locate any version of Langflow in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.10.3), your application is affected.

Note: The pip show langflow command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In Langflow, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary Before **Langflow 1.10.3**, several built-in components sent server-side HTTP requests to URLs the flow author controls, with no SSRF enforcement. An authenticated user who can build or run flows could make the Langflow server reach loopback, RFC 1918 / private networks, link-local addresses and cloud metadata endpoints (for example `http://169.254.169.254/latest/meta-data/`), and in many cases read the response back through the component output. Two things combined to cause this: 1. **Protection disabled / warn-only.** The SSRF guard (`lfx/utils/ssrf_protection.py`, added in 1.7.0 by #10544) shipped with `ssrf_protection_enabled = False`, and its only caller, the **API Request** component, called `validate_url_for_ssrf(url, warn_only=True)`. So even with protection turned on, blocked URLs were only logged. 2. **Inconsistent coverage.** Other components that take a user-supplied URL or base URL did not call the guard at all: RSS Reader, SearXNG, Web Search (fetching result / RSS URLs), Home Assistant, Glean Search and Docling Serve (remote). The problem was fixed across several PRs and is fully fixed in **Langflow 1.10.3** (and 1.11.0+). With the default settings, outbound requests from these components are now validated after DNS resolution, pinned to the validated IP (to prevent DNS rebinding) and **blocked** when they target private, loopback, link-local or metadata addresses, unless the operator allowlists the host. ### Affected versions | Package (PyPI) | Vulnerable | Patched | |---|---|---| | `langflow` | `< 1.10.3` | `1.10.3` | | `langflow-base` | `< 0.10.3` | `0.10.3` | | `lfx` | `< 1.10.3` | `1.10.3` | | `lfx-docling` (Docling Serve component) | `< 0.1.2` | `0.1.2` | How the fix rolled out: | Release | Change | |---|---| | `< 1.7.0` | No SSRF guard. All URL-taking components make unrestricted requests. | | `1.7.0` – `1.9.2` | Guard exists, but `ssrf_protection_enabled=False` by default and API Request uses `warn_only=True`. | | `1.9.3` | #13016: protection **on by default**, API Request **blocks** (DNS pinning / anti-rebinding). Other components still unprotected. | | `1.10.1` | #13395 (RSS Reader, SearXNG) and #13643 (Home Assistant, Glean, plus model-provider URL components) route requests through SSRF-safe helpers. | | `1.10.3` | #14033 (Docling Serve) and #14071 (Web Search result/RSS fetching). **All components cited in this report are protected.** | ### Details Vulnerable pattern (for example `rss.py` before #13395): ```python response = requests.get(self.rss_url, timeout=self.timeout) ``` API Request before #13016: ```python # TODO: In next major version (2.0), remove warn_only=True to enforce blocking validate_url_for_ssrf(url, warn_only=True) ``` with `ssrf_protection_enabled: bool = False` in the settings. **Clarifications on the original report.** Some sinks in the report are not exploitable SSRF: - `web_search.py`: the DuckDuckGo search request and the Google News RSS request, and `news_search.py:131`. The host is hard-coded (`html.duckduckgo.com` / `news.google.com`) and user input only goes into `quote_plus`-encoded path and query segments, so the destination cannot be redirected. The real Web Search sink was fetching the **result URLs**, which is fixed in #14071. - `langflow/load/utils.py` `get_flow()`: this is a client-side SDK helper (`from langflow.load import get_flow`) that the caller runs against their own Langflow URL. No API route calls it, so it is not a backend SSRF endpoint. ### PoC (vulnerable versions) 1. Log in as any user who can create flows. 2. Add an **RSS Reader** (or SearXNG / Home Assistant / Glean / Docling Serve) component and set its URL to `http://169.254.169.254/latest/meta-data/` (or an internal host such as `http://10.0.0.1/`). 3. Run the component. The Langflow server issues the request, and the response or error is shown in the component output. On patched versions the same run fails with `SSRFProtectionError: Access to IP address 169.254.169.254 is blocked by SSRF protection`. ### Impact - Access to cloud instance metadata (IAM credentials / tokens) on AWS, GCP and Azure deployments. - Probing and interaction with internal services and private networks reachable from the Langflow host. - Requires an authenticated account with permission to build or run flows. Deployments where every user is already fully trusted are less affected. ### Fix - **#13016**: sets `ssrf_protection_enabled = True` by default, changes `warn_only` to default `False`, drops `warn_only=True` from API Request, and adds `validate_and_resolve_url()` plus `SSRFProtectedTransport` (DNS pinning). ```diff - ssrf_protection_enabled: bool = False + ssrf_protection_enabled: bool = True ``` - **#13395**: adds `lfx.utils.ssrf_requests.ssrf_safe_get` (per-hop validation and pinning for `requests`) and uses it in RSS Reader and SearXNG. ```diff - response = requests.get(self.rss_url, timeout=self.timeout) + response = ssrf_safe_get(self.rss_url, timeout=self.timeout) ``` - **#13643**: adds `lfx.utils.ssrf_httpx` (`ssrf_safe_httpx_get/post`, protected client kwargs) and applies it to Home Assistant, Glean and the model-provider base-URL components. - **#14033**: Docling Serve builds its `httpx.Client` with `ssrf_protected_httpx_client_kwargs_for_url(base_url)`. - **#14071** (release-1.10.3) / **#14073** (forward-port to 1.11.0): Web Search validates and pins each result URL before fetching it, with redirects disabled. Note: connector-style components (for example Home Assistant, Ollama, LM Studio) keep a documented loopback exemption (#14146), so a self-hosted user can reach a local service on `localhost`. Private-network and metadata addresses stay blocked. Operators can tighten or relax this with `LANGFLOW_SSRF_ALLOWED_HOSTS` and `LANGFLOW_CONNECTOR_SSRF_VALIDATION_ENABLED`. ### Remediation - Upgrade to `langflow >= 1.10.3` (or `langflow-base >= 0.10.3` / `lfx >= 1.10.3` / `lfx-docling >= 0.1.2`). - Do not set `LANGFLOW_SSRF_PROTECTION_ENABLED=false`. If you need to reach internal hosts on purpose, allowlist only those hosts with `LANGFLOW_SSRF_ALLOWED_HOSTS`. - On versions that cannot be upgraded right away, restrict outbound network access from the Langflow host (for example, block `169.254.169.254` and use IMDSv2 on AWS).

GHSA-j8f7-x8jm-wmm4 Affected Langflow Versions

4 component(s)
Fixed Versions:
1.10.30.10.30.1.2
Product / Package Ecosystem Affected Versions Fixed Version
langflow
PyPI
< 1.10.3
1.10.3
langflow-base
PyPI
< 0.10.3
0.10.3
lfx
PyPI
< 1.10.3
1.10.3
lfx-docling
PyPI
< 0.1.2
0.1.2

References

Frequently Asked Questions

What is GHSA-j8f7-x8jm-wmm4?
GHSA-j8f7-x8jm-wmm4 is a security vulnerability in Langflow involving SSRF in URL-taking components (protection disabled by default / warn-only, not applied to RSS, SearXNG, Web Search, Home Assistant, Glean, Docling) under CWE-918: Server-Side Request Forgery (SSRF).
Which Langflow versions are affected?
Affected versions include releases prior to 1.10.3, 0.10.3, 0.1.2 across affected packages: langflow, langflow-base, lfx, lfx-docling.
What version fixes GHSA-j8f7-x8jm-wmm4?
Upgrading to 1.10.3, 0.10.3, 0.1.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is langflow affected?
Yes, langflow is affected in releases prior to 1.10.3. Upgrade your dependency to 1.10.3 or later.
Is langflow-base affected?
Yes, langflow-base is affected in releases prior to 0.10.3. Upgrade your dependency to 0.10.3 or later.
What CWE is associated with GHSA-j8f7-x8jm-wmm4?
GHSA-j8f7-x8jm-wmm4 is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check PyPI dependencies for GHSA-j8f7-x8jm-wmm4?
Run the dependency tree command: 'pip show langflow'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-j8f7-x8jm-wmm4",
  "modified" : "2026-10-06T13:39:58Z",
  "published" : "2026-10-06T13:39:57Z",
  "aliases" : [ ],
  "summary" : "Langflow: SSRF in URL-taking components (protection disabled by default / warn-only, not applied to RSS, SearXNG, Web Search, Home Assistant, Glean, Docling)",
  "details" : "### Summary\n\nBefore **Langflow 1.10.3**, several built-in components sent server-side HTTP requests to URLs the flow author controls, with no SSRF enforcement. An authenticated user who can build or run flows could make the Langflow server reach loopback, RFC 1918 / private networks, link-local addresses and cloud metadata endpoints (for example `http://169.254.169.254/latest/meta-data/`), and in many cases read the response back through the component output.\n\nTwo things combined to cause this:\n\n1. **Protection disabled / warn-only.** The SSRF guard (`lfx/utils/ssrf_protection.py`, added in 1.7.0 by #10544) shipped with `ssrf_protection_enabled = False`, and its only caller, the **API Request** component, called `validate_url_for_ssrf(url, warn_only=True)`. So even with protection turned on, blocked URLs were only logged.\n2. **Inconsistent coverage.** Other components that take a user-supplied URL or base URL did not call the guard at all: RSS Reader, SearXNG, Web Search (fetching result / RSS URLs), Home Assistant, Glean Search and Docling Serve (remote).\n\nThe problem was fixed across several PRs and is fully fixed in **Langflow 1.10.3** (and 1.11.0+). With the default settings, outbound requests from these components are now validated after DNS resolution, pinned to the validated IP (to prevent DNS rebinding) and **blocked** when they target private, loopback, link-local or metadata addresses, unless the operator allowlists the host.\n\n### Affected versions\n\n| Package (PyPI) | Vulnerable | Patched |\n|---|---|---|\n| `langflow` | `< 1.10.3` | `1.10.3` |\n| `langflow-base` | `< 0.10.3` | `0.10.3` |\n| `lfx` | `< 1.10.3` | `1.10.3` |\n| `lfx-docling` (Docling Serve component) | `< 0.1.2` | `0.1.2` |\n\nHow the fix rolled out:\n\n| Release | Change |\n|---|---|\n| `< 1.7.0` | No SSRF guard. All URL-taking components make unrestricted requests. |\n| `1.7.0` – `1.9.2` | Guard exists, but `ssrf_protection_enabled=False` by default and API Request uses `warn_only=True`. |\n| `1.9.3` | #13016: protection **on by default**, API Request **blocks** (DNS pinning / anti-rebinding). Other components still unprotected. |\n| `1.10.1` | #13395 (RSS Reader, SearXNG) and #13643 (Home Assistant, Glean, plus model-provider URL components) route requests through SSRF-safe helpers. |\n| `1.10.3` | #14033 (Docling Serve) and #14071 (Web Search result/RSS fetching). **All components cited in this report are protected.** |\n\n### Details\n\nVulnerable pattern (for example `rss.py` before #13395):\n\n```python\nresponse = requests.get(self.rss_url, timeout=self.timeout)\n```\n\nAPI Request before #13016:\n\n```python\n# TODO: In next major version (2.0), remove warn_only=True to enforce blocking\nvalidate_url_for_ssrf(url, warn_only=True)\n```\n\nwith `ssrf_protection_enabled: bool = False` in the settings.\n\n**Clarifications on the original report.** Some sinks in the report are not exploitable SSRF:\n\n- `web_search.py`: the DuckDuckGo search request and the Google News RSS request, and `news_search.py:131`. The host is hard-coded (`html.duckduckgo.com` / `news.google.com`) and user input only goes into `quote_plus`-encoded path and query segments, so the destination cannot be redirected. The real Web Search sink was fetching the **result URLs**, which is fixed in #14071.\n- `langflow/load/utils.py` `get_flow()`: this is a client-side SDK helper (`from langflow.load import get_flow`) that the caller runs against their own Langflow URL. No API route calls it, so it is not a backend SSRF endpoint.\n\n### PoC (vulnerable versions)\n\n1. Log in as any user who can create flows.\n2. Add an **RSS Reader** (or SearXNG / Home Assistant / Glean / Docling Serve) component and set its URL to `http://169.254.169.254/latest/meta-data/` (or an internal host such as `http://10.0.0.1/`).\n3. Run the component. The Langflow server issues the request, and the response or error is shown in the component output.\n\nOn patched versions the same run fails with `SSRFProtectionError: Access to IP address 169.254.169.254 is blocked by SSRF protection`.\n\n### Impact\n\n- Access to cloud instance metadata (IAM credentials / tokens) on AWS, GCP and Azure deployments.\n- Probing and interaction with internal services and private networks reachable from the Langflow host.\n- Requires an authenticated account with permission to build or run flows. Deployments where every user is already fully trusted are less affected.\n\n### Fix\n\n- **#13016**: sets `ssrf_protection_enabled = True` by default, changes `warn_only` to default `False`, drops `warn_only=True` from API Request, and adds `validate_and_resolve_url()` plus `SSRFProtectedTransport` (DNS pinning).\n\n  ```diff\n  -    ssrf_protection_enabled: bool = False\n  +    ssrf_protection_enabled: bool = True\n  ```\n- **#13395**: adds `lfx.utils.ssrf_requests.ssrf_safe_get` (per-hop validation and pinning for `requests`) and uses it in RSS Reader and SearXNG.\n\n  ```diff\n  -            response = requests.get(self.rss_url, timeout=self.timeout)\n  +            response = ssrf_safe_get(self.rss_url, timeout=self.timeout)\n  ```\n- **#13643**: adds `lfx.utils.ssrf_httpx` (`ssrf_safe_httpx_get/post`, protected client kwargs) and applies it to Home Assistant, Glean and the model-provider base-URL components.\n- **#14033**: Docling Serve builds its `httpx.Client` with `ssrf_protected_httpx_client_kwargs_for_url(base_url)`.\n- **#14071** (release-1.10.3) / **#14073** (forward-port to 1.11.0): Web Search validates and pins each result URL before fetching it, with redirects disabled.\n\nNote: connector-style components (for example Home Assistant, Ollama, LM Studio) keep a documented loopback exemption (#14146), so a self-hosted user can reach a local service on `localhost`. Private-network and metadata addresses stay blocked. Operators can tighten or relax this with `LANGFLOW_SSRF_ALLOWED_HOSTS` and `LANGFLOW_CONNECTOR_SSRF_VALIDATION_ENABLED`.\n\n### Remediation\n\n- Upgrade to `langflow >= 1.10.3` (or `langflow-base >= 0.10.3` / `lfx >= 1.10.3` / `lfx-docling >= 0.1.2`).\n- Do not set `LANGFLOW_SSRF_PROTECTION_ENABLED=false`. If you need to reach internal hosts on purpose, allowlist only those hosts with `LANGFLOW_SSRF_ALLOWED_HOSTS`.\n- On versions that cannot be upgraded right away, restrict outbound network access from the Langflow host (for example, block `169.254.169.254` and use IMDSv2 on AWS).",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "langflow"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.10.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "langflow-base"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.10.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "lfx"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.10.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "lfx-docling"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.1.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/langflow-ai/langflow/security/advisories/GHSA-j8f7-x8jm-wmm4"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/langflow-ai/langflow/pull/13016"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/langflow-ai/langflow/pull/13395"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/langflow-ai/langflow/pull/13643"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/langflow-ai/langflow/pull/14033"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/langflow-ai/langflow/pull/14071"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/langflow-ai/langflow/commit/94859df33acd70b2a1f816e26d68f5e89a7e5639"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/langflow-ai/langflow"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/langflow-ai/langflow/releases/tag/v1.10.3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-06T13:39:57Z",
    "nvd_published_at" : null
  }
}