Skip to content

Product

ibm langflow oss vulnerabilities

176 published CVES affecting ibm langflow oss, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
176
Critical
42
High
84
Medium
50
Low
0
Unscored
0
CISA KEV
1

Latest ibm langflow oss CVEs

Newest publication first · page 1 of 8

  1. HighCVSS 8.1 EPSS 0.39%

    IBM Langflow OSS 1.0.0 through 1.12.2 An authenticated flow author could write attacker-controlled file content into any directory writable by the service account, bypassing the platform's local file access isolation safeguard. Via a crafted on-disk index, the attacker could also...

  2. CriticalCVSS 9.8 EPSS 0.52%

    IBM Langflow OSS 1.0.0 through 1.12.4 could allow a remote attacker to trigger pre-existing stored Python component code in a public workflow, executing it under the flow owner's runtime context within the server process. This bypasses the intended trust boundary where public exe...

  3. MediumCVSS 6.8 EPSS 0.25%

    IBM Langflow OSS 1.0.0 through 1.12.3 could allow an authenticated attacker to produce a server-generated ZIP archive containing entry paths that traverse outside the intended extraction directory. Extraction of the archive by a victim using a non-sanitizing tool could result in...

  4. MediumCVSS 4.3 EPSS 0.21%

    IBM Langflow OSS 1.0.0 through 1.12.3 is vulnerable to server-side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks.

  5. MediumCVSS 6.5 EPSS 0.33%

    IBM Langflow OSS 1.0.0 through 1.12.3 could allow an authenticated attacker to cancel any victim's running background workflow job by sending a single HTTP request, resulting in loss of in-progress compute work with no flow-level permission check.

  6. MediumCVSS 5.4 EPSS 0.18%

    IBM Langflow OSS 1.0.0 through 1.12.3 is vulnerable to server-side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.