A critical Langflow vulnerability, CVE-2026-105697, allows remote code execution with a CVSS score of 9.9 — about as bad as it gets. Over 1,400 live exploit attempts were recorded in October 2026. And here is the trap: the first fix, shipped in Langflow 1.9.0, was incomplete — it did not fully close the hole. The real, complete fix only landed in Langflow 1.10.3. If you upgraded to 1.9.0 and stopped there, you are still exposed. Type your Langflow version below and the checker grades you in one second. Free, no signup.
langflow --version, upgrade to 1.10.3+ immediately, and take any internet-exposed vulnerable instance offline until you do.
Find your version with langflow --version or on the Langflow settings page. Type it below (e.g. 1.8.2, 1.9.0, 1.10.3).
This checker grades version numbers against the published patch boundary (1.10.3). It does not scan your server for actual exploitation.
CVE-2026-105697 is a critical remote code execution vulnerability in Langflow with a CVSS score of 9.9. A first fix shipped in Langflow 1.9.0 was later found to be incomplete, so attackers could still exploit patched instances; the complete fix landed in 1.10.3. Over 1,400 live exploit attempts were recorded in October 2026.
Langflow is safe to use only if you are on version 1.10.3 or later. CVE-2026-105697 is a CVSS 9.9 remote code execution flaw affecting everything below 1.10.3 — including versions patched with the incomplete 1.9.0 fix. Upgrade to 1.10.3+ and verify the version before exposing Langflow to any network.
CVE-2026-105697 is a critical remote code execution vulnerability in Langflow with a CVSS score of 9.9. A first fix shipped in Langflow 1.9.0 was later found to be incomplete, so attackers could still exploit patched instances; the complete fix landed in 1.10.3. Over 1,400 live exploit attempts were recorded in October 2026.
Yes. The 1.9.0 patch for CVE-2026-105697 was incomplete and did not fully close the remote code execution vector. Any version from 1.9.0 up to 1.10.2 is still at risk. Only 1.10.3 and later carry the complete fix — upgrade from 1.9.0 anyway.
Run 'langflow --version' in your terminal, or check the bottom of the Langflow settings page in the UI. Compare the result against the safe floor: 1.10.3. Anything lower — including 1.9.0 through 1.10.2 — needs upgrading. The checker on this page does the grading for you.
Upgrade to Langflow 1.10.3 or later immediately, take any internet-exposed instance offline until upgraded, rotate credentials and API keys the instance could have seen, and review logs for suspicious activity. The HowTo section below walks through the fix step by step.
Informational only: this page reflects the published CVE-2026-105697 record and Langflow release notes. It is not a security audit or legal advice. Verify against the project's official changelog before acting.
Filed under Cybersecurity News by Ingenious AI — see the related checks above for more in this series.