CVE-2026-9135
Langflow ToolGuard code injection permits authenticated remote Python execution
Is CVE-2026-9135 being exploited?
Not confirmed. CVE-2026-9135 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.84% probability of exploitation in the next 30 days.
How severe is CVE-2026-9135?
CVE-2026-9135 is rated Critical with a CVSS score of 9.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-9135?
Yes. A fix has been recorded for CVE-2026-9135. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-9135 affect?
CVE-2026-9135 affects IBM Langflow OSS <=1.10.0 (<=1.9.2 confirmed), ToolGuard integration (CodeInput dynamic fields), agentic MCP update_flow_component_field tool, Deployments with AUTO_LOGIN=true or NEW_USER_IS_ACTIVE=true. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-9135?
Disable AUTO_LOGIN/NEW_USER_IS_ACTIVE; restrict flow creation and MCP API; apply vendor patch when available.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated users with flow-creation rights can execute arbitrary Python on the server and perform cross-tenant compromise via MCP API.
Immediate action required
- affected>= 1.0.0 and <= 1.10.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.