Medium, CVSS 6.3PyPIAmendedPublished
Langflow: SSRF in URL-taking components (protection disabled by default / warn-only, not applied to RSS, SearXNG, Web Search, Home Assistant, Glean, Docling)
GHSA-j8f7-x8jm-wmm4
- Affected
- PyPI lfx-docling < 0.1.2
- Fixed in
- 0.1.2· Vendor fix available
- Issue
- 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,…
Recommended action: Upgrade to 0.1.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.