Langflow is vulnerable to server-side request forgery due to missing egress validation on server-side URL fetches

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps IBM/Langflow OSS (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for IBM/Langflow OSS.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Sep 10, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 10, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 10, 2026

Sources and claim methodology

• Source referenceibm.com

Related CVEs

• Langflow is vulnerable to arbitrary code execution due to multiple incomplete code security controls and missing execution guardsSame ibm/langflow oss package
• Langflow is vulnerable to arbitrary code execution due to multiple incomplete code security controls and missing execution guardsSame ibm/langflow oss package
• Langflow is vulnerable to arbitrary code execution due to multiple incomplete code security controls and missing execution guardsSame ibm/langflow oss package
• Langflow is vulnerable to arbitrary code execution due to multiple incomplete code security controls and missing execution guardsSame ibm/langflow oss package
• Langflow is vulnerable to server-side request forgery due to missing egress validation on server-side URL fetchesSame ibm/langflow oss package
• Langflow is vulnerable to arbitrary code execution due to multiple incomplete code security controls and missing execution guardsSame ibm/langflow oss package