Critical Langflow Flaw CVE-2026-33017 Triggers Attacks
Basically, a serious bug in Langflow lets hackers run harmful code easily.
A critical flaw in Langflow allows remote code execution, with attacks starting just 20 hours after disclosure. All versions before 1.8.1 are affected, raising significant security concerns. Immediate updates and audits are essential to protect sensitive data.
The Flaw
CVE-2026-33017 is a critical security vulnerability found in Langflow, an open-source AI platform. This flaw, rated at a CVSS score of 9.3, involves missing authentication combined with code injection. Attackers can exploit this vulnerability to execute arbitrary code remotely. The issue lies in the /api/v1/build_public_tmp/{flow_id}/flow endpoint, which allows public flows to be built without authentication. When attackers provide malicious data, the system executes their code using exec() without any safeguards.
This vulnerability affects all versions of Langflow prior to 1.8.1. The developers have addressed the issue in version 1.9.0.dev8. Security researcher Aviral Srivastava, who discovered the flaw, indicates that the root cause is similar to another critical bug, CVE-2025-3248. Both vulnerabilities utilize the same exec() function, which is the source of the problem. The real fix involves removing the data parameter from the public endpoint to prevent unauthorized code execution.
What's at Risk
Successful exploitation of CVE-2026-33017 can lead to unauthenticated remote code execution with full server privileges. This means attackers can read environment variables, modify files, and inject backdoors. They can even obtain a reverse shell, allowing them to control the server completely. The ease of exploitation is alarming; a single HTTP POST request with malicious Python code can trigger the attack. This vulnerability poses a significant risk to organizations using Langflow, especially those with sensitive data.
Patch Status
The first exploitation attempts were observed within 20 hours of the vulnerability's public disclosure. This rapid response from attackers highlights a troubling trend: the median time-to-exploit for vulnerabilities is shrinking dramatically. Organizations typically take about 20 days to deploy patches, leaving them vulnerable during this period. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has noted that attackers are monitoring vulnerability advisories closely, often launching attacks before organizations can respond.
Immediate Actions
Organizations using Langflow should update to the latest patched version immediately. Additionally, they should audit environment variables and secrets on any publicly exposed instances. Key actions include:
- Rotate keys and database passwords as a precautionary measure.
- Monitor for unusual outbound connections to detect potential exploitation.
- Restrict network access to Langflow instances using firewall rules or a reverse proxy with authentication.
This incident serves as a stark reminder of the vulnerabilities in popular open-source tools. As AI workloads become more integrated into business operations, they are increasingly targeted by cybercriminals. Organizations must adapt their vulnerability management strategies to keep pace with the rapidly evolving threat landscape.
The Hacker News