CVE-2025-68477: CWE-918: Server-Side Request Forgery (SSRF) in langflow-ai langflow
Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to version 1.7.0, Langflow provides an API Request component that can issue arbitrary HTTP requests within a flow. This component takes a user-supplied URL, performs only normalization and basic format checks, and then sends the request using a server-side httpx client. It does not block private IP ranges (127[.]0[.]0[.]1, the 10/172/192 ranges) or cloud metadata endpoints (169[.]254[.]169[.]254), and it returns the response body as the result. Because the flow execution endpoints (/api/v1/run, /api/v1/run/advanced) can be invoked with just an API key, if an attacker can control the API Request URL in a flow, non-blind SSRF is possible—accessing internal resources from the server’s network context. This enables requests to, and collection of responses from, internal administrative endpoints, metadata services, and internal databases/services, leading to information disclosure and providing a foothold for further attacks. Version 1.7.0 contains a patch for this issue.
AI Analysis
Technical Summary
CVE-2025-68477 is a Server-Side Request Forgery (SSRF) vulnerability identified in the langflow AI tool, specifically affecting versions prior to 1.7.0. Langflow provides an API Request component that allows users to specify URLs for HTTP requests executed server-side using the httpx client. The vulnerability stems from insufficient validation of user-supplied URLs: the component performs only normalization and basic format checks but does not block requests to private IP ranges (such as 127.0.0.1, 10.x.x.x, 172.x.x.x, 192.x.x.x) or cloud metadata service endpoints (169.254.169.254). Because the flow execution endpoints (/api/v1/run and /api/v1/run/advanced) can be invoked with just an API key, an attacker who can control the URL parameter in a flow can cause the server to issue arbitrary HTTP requests within its internal network context. This non-blind SSRF enables attackers to access internal administrative interfaces, cloud metadata services, and internal databases or services that are otherwise inaccessible externally. The vulnerability allows attackers to retrieve sensitive information, such as credentials or configuration data, which can be leveraged for further lateral movement or privilege escalation. The CVSS v3.1 base score is 7.7 (high), reflecting network attack vector, low complexity, low privileges required, no user interaction, and a scope change with high confidentiality impact but no integrity or availability impact. The vulnerability was published on December 19, 2025, and patched in langflow version 1.7.0. No known exploits in the wild have been reported yet. Organizations using langflow in AI automation workflows should prioritize upgrading to the patched version to prevent exploitation.
Potential Impact
For European organizations, the impact of CVE-2025-68477 can be significant, especially for those leveraging langflow to automate AI-powered workflows that interact with internal systems. Exploitation could lead to unauthorized disclosure of sensitive internal data, including cloud metadata that may contain credentials or tokens for further access. This can compromise confidentiality and potentially enable attackers to pivot within the network, access internal administrative endpoints, or exfiltrate data. Given the increasing adoption of AI tools and cloud services in Europe, organizations running langflow on cloud infrastructure or within private networks are at risk of internal network reconnaissance and data leakage. The vulnerability could also undermine trust in AI automation platforms and lead to regulatory compliance issues under GDPR if personal or sensitive data is exposed. The absence of known exploits reduces immediate risk but does not eliminate the threat, as attackers may develop exploits rapidly once the vulnerability is public. The requirement of an API key limits exposure but does not eliminate risk, especially if API keys are leaked or insufficiently protected.
Mitigation Recommendations
European organizations should take the following specific mitigation steps: 1) Immediately upgrade langflow installations to version 1.7.0 or later, which contains the patch that properly restricts SSRF vectors. 2) Audit and restrict API key distribution and usage to minimize the risk of unauthorized access to flow execution endpoints. 3) Implement network segmentation and firewall rules to limit the server's ability to access sensitive internal IP ranges and cloud metadata endpoints, adding a defense-in-depth layer. 4) Monitor API usage logs for unusual or unexpected requests targeting internal IP ranges or metadata endpoints. 5) Employ runtime application self-protection (RASP) or web application firewalls (WAFs) that can detect and block SSRF patterns. 6) Conduct internal security assessments and penetration tests focusing on SSRF and internal resource access via AI workflow tools. 7) Educate developers and administrators about the risks of SSRF in AI automation platforms and enforce secure coding and configuration practices. These steps go beyond generic advice by focusing on controlling API key access, network-level restrictions, and active monitoring tailored to the langflow environment.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Ireland, Belgium, Denmark
CVE-2025-68477: CWE-918: Server-Side Request Forgery (SSRF) in langflow-ai langflow
Description
Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to version 1.7.0, Langflow provides an API Request component that can issue arbitrary HTTP requests within a flow. This component takes a user-supplied URL, performs only normalization and basic format checks, and then sends the request using a server-side httpx client. It does not block private IP ranges (127[.]0[.]0[.]1, the 10/172/192 ranges) or cloud metadata endpoints (169[.]254[.]169[.]254), and it returns the response body as the result. Because the flow execution endpoints (/api/v1/run, /api/v1/run/advanced) can be invoked with just an API key, if an attacker can control the API Request URL in a flow, non-blind SSRF is possible—accessing internal resources from the server’s network context. This enables requests to, and collection of responses from, internal administrative endpoints, metadata services, and internal databases/services, leading to information disclosure and providing a foothold for further attacks. Version 1.7.0 contains a patch for this issue.
AI-Powered Analysis
Technical Analysis
CVE-2025-68477 is a Server-Side Request Forgery (SSRF) vulnerability identified in the langflow AI tool, specifically affecting versions prior to 1.7.0. Langflow provides an API Request component that allows users to specify URLs for HTTP requests executed server-side using the httpx client. The vulnerability stems from insufficient validation of user-supplied URLs: the component performs only normalization and basic format checks but does not block requests to private IP ranges (such as 127.0.0.1, 10.x.x.x, 172.x.x.x, 192.x.x.x) or cloud metadata service endpoints (169.254.169.254). Because the flow execution endpoints (/api/v1/run and /api/v1/run/advanced) can be invoked with just an API key, an attacker who can control the URL parameter in a flow can cause the server to issue arbitrary HTTP requests within its internal network context. This non-blind SSRF enables attackers to access internal administrative interfaces, cloud metadata services, and internal databases or services that are otherwise inaccessible externally. The vulnerability allows attackers to retrieve sensitive information, such as credentials or configuration data, which can be leveraged for further lateral movement or privilege escalation. The CVSS v3.1 base score is 7.7 (high), reflecting network attack vector, low complexity, low privileges required, no user interaction, and a scope change with high confidentiality impact but no integrity or availability impact. The vulnerability was published on December 19, 2025, and patched in langflow version 1.7.0. No known exploits in the wild have been reported yet. Organizations using langflow in AI automation workflows should prioritize upgrading to the patched version to prevent exploitation.
Potential Impact
For European organizations, the impact of CVE-2025-68477 can be significant, especially for those leveraging langflow to automate AI-powered workflows that interact with internal systems. Exploitation could lead to unauthorized disclosure of sensitive internal data, including cloud metadata that may contain credentials or tokens for further access. This can compromise confidentiality and potentially enable attackers to pivot within the network, access internal administrative endpoints, or exfiltrate data. Given the increasing adoption of AI tools and cloud services in Europe, organizations running langflow on cloud infrastructure or within private networks are at risk of internal network reconnaissance and data leakage. The vulnerability could also undermine trust in AI automation platforms and lead to regulatory compliance issues under GDPR if personal or sensitive data is exposed. The absence of known exploits reduces immediate risk but does not eliminate the threat, as attackers may develop exploits rapidly once the vulnerability is public. The requirement of an API key limits exposure but does not eliminate risk, especially if API keys are leaked or insufficiently protected.
Mitigation Recommendations
European organizations should take the following specific mitigation steps: 1) Immediately upgrade langflow installations to version 1.7.0 or later, which contains the patch that properly restricts SSRF vectors. 2) Audit and restrict API key distribution and usage to minimize the risk of unauthorized access to flow execution endpoints. 3) Implement network segmentation and firewall rules to limit the server's ability to access sensitive internal IP ranges and cloud metadata endpoints, adding a defense-in-depth layer. 4) Monitor API usage logs for unusual or unexpected requests targeting internal IP ranges or metadata endpoints. 5) Employ runtime application self-protection (RASP) or web application firewalls (WAFs) that can detect and block SSRF patterns. 6) Conduct internal security assessments and penetration tests focusing on SSRF and internal resource access via AI workflow tools. 7) Educate developers and administrators about the risks of SSRF in AI automation platforms and enforce secure coding and configuration practices. These steps go beyond generic advice by focusing on controlling API key access, network-level restrictions, and active monitoring tailored to the langflow environment.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-12-18T18:29:07.308Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 694583dbf063e4fadffb129e
Added to database: 12/19/2025, 4:56:59 PM
Last enriched: 12/19/2025, 5:11:58 PM
Last updated: 12/19/2025, 6:00:15 PM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-14958: Heap-based Buffer Overflow in floooh sokol
MediumCVE-2025-68478: CWE-73: External Control of File Name or Path in langflow-ai langflow
HighCVE-2025-68430: CWE-24: Path Traversal: '../filedir' in cvat-ai cvat
MediumCVE-2025-63665: n/a
UnknownCVE-2025-14957: NULL Pointer Dereference in WebAssembly Binaryen
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.