IBM Langflow OSS vulnerabilities
6 CVEs affecting IBM Langflow OSS, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2026-12944, published 2026-09-14.
More from IBM.
Highest priority
Known exploited (CISA KEV) first, then by EPSS exploit probability.
- CVE-2026-12944, published 2026-09-14. Critical severity, CVSS 9.6. EPSS: 0.4% chance of exploitation in the next 30 days. IBM Langflow OSS 1.0.0 through 1.10.0 can allow attackers to execute arbitrary Python code with root privileges (UID=0) on the Langflow server by submitting components containing socket or urllib…
- CVE-2026-17628, published 2026-09-14. Medium severity, CVSS 5.4. EPSS: 0.3% chance of exploitation in the next 30 days. IBM Langflow OSS 1.0.0 through 1.10.2 could allow a remote authenticated attacker to change the password of an account due to improper authentication.
- CVE-2026-12767, published 2026-09-14. Medium severity, CVSS 6.5. EPSS: 0.2% chance of exploitation in the next 30 days. IBM Langflow OSS 1.0.0 through 1.11.5 is vulnerable to server-side request forgery (SSRF). This may allow an unauthenticated attacker to send unauthorized requests from the system, potentially…
- CVE-2026-12765, published 2026-09-14. Medium severity, CVSS 6.5. EPSS: 0.2% chance of exploitation in the next 30 days. IBM Langflow OSS 1.0.0 through 1.10.2 is vulnerable to server-side request forgery (SSRF). This may allow an unauthenticated attacker to send unauthorized requests from the system, potentially…
- CVE-2026-12766, published 2026-09-14. Medium severity, CVSS 5.4. EPSS: 0.2% chance of exploitation in the next 30 days. IBM Langflow OSS 1.0.0 through 1.11.2 is vulnerable to server-side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading…
- CVE-2026-12763, published 2026-09-14. Medium severity, CVSS 4.2. EPSS: 0.1% chance of exploitation in the next 30 days. IBM Langflow OSS 1.0.0 through 1.11.5 could allow an authenticated attacker to access another user's MCP server context due to improper cache key isolation in the MCP Tools component.