Server-side Request Forgery (SSRF) Affecting langflow-base package, versions [,0.10.3)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-PYTHON-LANGFLOWBASE-21693720
- published24 Oct 2026
- disclosed6 Oct 2026
- creditUnknown
Introduced: 6 Oct 2026
New CVE NOT AVAILABLE CWE-918 (opens in a new tab)How to fix?
Upgrade langflow-base to version 0.10.3 or higher.
Overview
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the API request component and related URL-taking components (RSS, SearXNG, Web Search, Home Assistant, Glean, Docling), which lack SSRF protection by default. An authenticated attacker can supply a URL that resolves to an internal or metadata address, causing the server to make outbound requests to private networks, loopback interfaces, link-local addresses, or cloud metadata endpoints (AWS, GCP, Azure). Additionally, the absence of DNS pinning creates a TOCTOU race where a hostname passes the SSRF check but is re-resolved to a private IP for the actual request, enabling DNS rebinding attacks.
Note: This is only exploitable against internal resources that are reachable from the server's network; exploitation requires the attacker to have at least authenticated (low-privilege) access to submit URLs to the affected components.