CVE-2026-9201: Langflow OSS is affected by arbitrary code execution in component generation, validation, and custom component handling
IBM Langflow OSS 1.0.0 through 1.10.3 could allow an authenticated attacker to execute arbitrary code due to a cryptographic weakness in the custom component validation mechanism. When the optional hardening mode that restricts execution to trusted component templates is enabled, the application validates component code using a truncated SHA‑256 hash. Because the hash comparison relies on only a portion of the digest, an attacker can craft malicious component code that collides with a trusted template hash and bypasses validation. Successful exploitation allows the attacker to introduce and execute unauthorized Python code within the Langflow process, defeating the intended security control and potentially leading to full compromise of the affected instance.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
IBM Langflow OSSto a version that resolves this vulnerability.Fixed in 1.11.0 - Upgrade
Upgrade
IBM Langflow OSSto a version that resolves this vulnerability.Fixed in 1.10.3
Event History
Frequently Asked Questions
What is the severity of CVE-2026-9201?
CVE-2026-9201 has a severity score of 71, indicating a significant security risk.
How do I fix CVE-2026-9201?
To mitigate CVE-2026-9201, ensure that the hardening mode is enabled to restrict the execution to trusted component templates and review custom validation mechanisms.
What type of vulnerability is CVE-2026-9201?
CVE-2026-9201 is a vulnerability that allows for arbitrary code execution due to a cryptographic weakness in component validation.
Who is affected by CVE-2026-9201?
CVE-2026-9201 affects users of IBM Langflow OSS who utilize the custom component validation mechanism.
When was CVE-2026-9201 published?
CVE-2026-9201 was published on August 5, 2026.