Langflow: SSRF in URL-taking components (protection disabled by default / warn-only, not applied to RSS, SearXNG, Web Search, Home Assistant, Glean, Docling)
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (langflow-base 0.10.3; lfx-docling 0.1.2; lfx 1.10.3; langflow 1.10.3), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI langflow-base
- Affected
- < 0.10.3
- Fixed in
- 0.10.3
PyPI lfx-docling
- Affected
- < 0.1.2
- Fixed in
- 0.1.2
PyPI lfx
- Affected
- < 1.10.3
- Fixed in
- 1.10.3
PyPI langflow
- Affected
- < 1.10.3
- Fixed in
- 1.10.3
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-j8f7-x8jm-wmm4 lists affected ranges: PyPI langflow >=0 =0 =0 =0 <0.1.2
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-j8f7-x8jm-wmm4 lists affected ranges: PyPI langflow >=0 =0 =0 =0 <0.1.2 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 6.3 · 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 · score source
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
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/ssrfprotection.py, added in 1.7.0 by #10544) shipped with ssrfprotectionenabled = False, and its only caller, the API Request component, called validateurlforssrf(url, warnonly=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,…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 4 · amended ·
Amended from ghsa record GHSA-j8f7-x8jm-wmm4
- Revision 3 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 2 · amended ·
Amended from osv record GHSA-j8f7-x8jm-wmm4
- Revision 1 · created ·
Published from ghsa record GHSA-j8f7-x8jm-wmm4
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-j8f7-x8jm-wmm4 Advisory: Langflow: SSRF in URL-taking components (protection disabled by default / warn-only, not applied to RSS, SearXNG, Web Search, Home Assistant, Glean, Docling) IDs: GHSA-j8f7-x8jm-wmm4 Record: https://patchnext.com/advisories/ghsa-j8f7-x8jm-wmm4 (revision 4, source checked 26 Oct 2026, 13:55 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: langflow-base 0.10.3; lfx-docling 0.1.2; lfx 1.10.3; langflow 1.10.3. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI langflow-base: affected < 0.10.3; fixed in 0.10.3 - PyPI lfx-docling: affected < 0.1.2; fixed in 0.1.2 - PyPI lfx: affected < 1.10.3; fixed in 1.10.3 - PyPI langflow: affected < 1.10.3; fixed in 1.10.3 ## Suggested inspection (read-only) - `python -m pip show langflow-base`: prints the installed version. Run with the environment that serves production active. - `python -m pip show lfx-docling`: prints the installed version. Run with the environment that serves production active. - `python -m pip show lfx`: prints the installed version. Run with the environment that serves production active. - `python -m pip show langflow`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on langflow-base, lfx-docling, lfx, langflow. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-j8f7-x8jm-wmm4 (GitHub-reviewed advisory GHSA-j8f7-x8jm-wmm4 lists affected ranges: PyPI langflow >=0 =0 =0 =0 <0.1.2) - Verified: https://osv.dev/vulnerability/GHSA-j8f7-x8jm-wmm4 (OSV record GHSA-j8f7-x8jm-wmm4 lists affected ranges: PyPI langflow >=0 =0 =0 =0 <0.1.2 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…