CVE-2026-9201
Authenticated hash-collision allows arbitrary Python code execution in IBM Langflow.
Is CVE-2026-9201 being exploited?
Not confirmed. CVE-2026-9201 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.23% probability of exploitation in the next 30 days.
How severe is CVE-2026-9201?
CVE-2026-9201 is rated High with a CVSS score of 8.8. 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-9201?
Yes. A fix has been recorded for CVE-2026-9201. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-9201 affect?
CVE-2026-9201 affects IBM Langflow OSS 1.0.0 - 1.10.3. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-9201?
Apply vendor patch when available or disable hardening mode; restrict access and rotate credentials.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker crafts component colliding with truncated SHA-256, bypasses template validation and executes arbitrary Python in the Langflow process, risking full instance compromise.
Immediate action required
- affected>= 1.0.0 and <= 1.10.3
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.