Missing Authentication for Critical Function Affecting langflow-base package, versions [,0.8.1)
Threat Intelligence
Snyk has reported that there have been attempts or successful attacks targeting this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Missing Authentication for Critical Function vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-PYTHON-LANGFLOWBASE-15680351
- published18 Mar 2026
- disclosed17 Mar 2026
- creditAviral Srivastava
Introduced: 17 Mar 2026
CVE-2026-33017 (opens in a new tab)How to fix?
Upgrade langflow-base to version 0.8.1 or higher.
Overview
Affected versions of this package are vulnerable to Missing Authentication for Critical Function in the POST /api/v1/build_public_tmp/{flow_id}/flow endpoint when attacker-controlled flow data is supplied to the data parameter, which is then executed using exec() without authentication or sandboxing. An attacker can execute arbitrary code on the server by submitting malicious flow definitions containing executable Python code. This is only exploitable if the instance has at least one public flow and the attacker knows the public flow's UUID, which can be discovered via shared links or URLs.
Workaround
Remove the data parameter from build_public_tmp. Public flows should only execute their stored flow data, never attacker-supplied data.