Critical Langflow Flaw CVE-2026-33017 Triggers Attacks within 20 Hours of Disclosure

A critical security flaw in Langflow (CVE-2026-33017, CVSS 9.3) was exploited by threat actors within 20 hours of disclosure, highlighting the rapid speed at which vulnerabilities are now being weaponized.
A critical security flaw impacting Langflow has come under active exploitation within 20 hours of public disclosure, highlighting the speed at which threat actors weaponize newly published vulnerabilities.
The security defect, tracked as CVE-2026-33017 (CVSS score: 9.3), is a case of missing authentication combined with code injection that could result in remote code execution.
"The POST /api/v1/build_public_tmp/{flow_id}/flow endpoint allows building public flows without requiring authentication," according to Langflow's advisory for the flaw. When the optional data parameter is supplied, the endpoint uses attacker-controlled flow data instead of the stored flow data from the database. This code is passed to exec() with zero sandboxing, resulting in unauthenticated remote code execution.
The vulnerability affects all versions of the open-source artificial intelligence (AI) platform prior to and including 1.8.1. It has been currently addressed in the development version 1.9.0.dev8.
Security researcher Aviral Srivastava, who discovered the flaw, noted it is distinct from CVE-2025-3248. Cloud security firm Sysdig observed the first exploitation attempts within 20 hours of the advisory's publication on March 17, 2026, even without public PoC code. Attackers built working exploits directly from the advisory description.
Threat actors have been observed moving from automated scanning to leveraging custom Python scripts to extract sensitive data like "/etc/passwd" and environment variables. This timeline compression poses serious challenges for defenders, as the median time for organizations to deploy patches is approximately 20 days, while attackers are now weaponizing flaws in mere hours.
Users are advised to update to the latest patched version immediately, audit environment variables, rotate keys, and restrict network access to Langflow instances using firewall rules or a reverse proxy with authentication.
Source: The Hacker News
















