PoC Monitor
← All CVEs
CVE-2026-107329published 29 Oct 2026 15:16 UTCData: JSON · API

IBM Langflow OSS

Langflow OSS is affected by multiple vulnerabilities

IBM Langflow OSS 1.0.0 through 1.12.4 could allow a remote authenticated attacker to execute arbitrary code due to improper control of code generation.

First public PoC 35 days beforebefore publication · 25 Sep 2026
Public PoCs11 on GitHub
CVSS9.9critical · scored by CNA · CWE-94
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

IBM Langflow OSS
  • >= 1.0.0, <= 1.12.4

Mitigation

IBM strongly recommends addressing the vulnerability now by upgrading Langflow OSS to version 1.12.5. https://pypi.org/project/langflow/1.12.5/ For Langflow OSS versions 1.0.0 - 1.12.4, follow the Prepare to upgrade instructions and release-specific configuration changes https://docs.langflow.org/release-notes , including backing up your existing installation, then follow the Langflow OSS installation instructions https://docs.langflow.org/get-started-installation to install version 1.12.5 and test your flows. For deployments using MCP stdio, also apply the configuration controls in Workarounds and Mitigations. This bulletin also discloses fixes delivered in prior releases: CVE-2026-107366 was fixed in version 1.9.0; CVE-2026-18894 was fixed in version 1.11.2; and CVE-2026-77817 was fixed in version 1.11.5. Version 1.12.5 includes these fixes.

Workaround

IBM strongly recommends applying the following configuration controls to deployments using MCP stdio in addition to upgrading Langflow OSS to version 1.12.5. These controls do not replace the upgrade. Set LANGFLOW_MCP_SERVER_INTERPRETER_HARDENING=true to reject direct shell-script execution, and set LANGFLOW_CUSTOM_COMPONENT_ADMIN_ONLY=true to block non-admin MCP stdio access. Restart the Langflow service after updating its environment configuration. These restrictions can require changes to existing MCP server launch configurations and limit which users can use MCP stdio. For public workflows, retain the default restriction on custom components. Explicitly enabling LANGFLOW_ALLOW_PUBLIC_CUSTOM_COMPONENTS permits custom component execution and changes the default protection described for CVE-2026-18894. For CVE-2026-77817, upgrading prevents the identified secret disclosure in new flow and project exports. Revoke or rotate any credentials exposed in previously exported files; upgrading does not remove secrets from copies already exported.

References

Timeline

Days relative to CVE publication
-35-28-21-14-7t=0+7First public PoC25 Sep 2026 · t−35dCVE published29 Oct 2026 · t = 0

First public PoC 35 days before publication; not in CISA KEV. First PoC: rmhowe425/POC-CVE-2026-107329 (created 25 Sep 2026, found by us: backfilled).

PoC repositories

Found on GitHub.

1 PoCs

PoCs 1
RepositoryCreatedStarsAssessment
rmhowe425/POC-CVE-2026-107329 25 Sep 2026 −35 d 2 PoC

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.