langflow-ai Langflow up to 1.8.1 Public Flow Build Endpoint eval injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in langflow-ai Langflow up to 1.8.1 and classified as critical. Affected is an unknown function of the component Public Flow Build Endpoint. The manipulation leads to eval injection. This vulnerability is referenced as CVE-2026-33017. Remote exploitation of the attack is possible. Furthermore, an exploit is available.
Details
A vulnerability, which was classified as critical, has been found in langflow-ai Langflow up to 1.8.1. This issue affects an unknown part of the component Public Flow Build Endpoint. The manipulation with an unknown input leads to a eval injection vulnerability. Using CWE to declare the problem leads to CWE-95. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. "eval"). Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Langflow is a tool for building and deploying AI-powered agents and workflows. In versions prior to 1.9.0, the POST /api/v1/build_public_tmp/{flow_id}/flow endpoint allows building public flows without requiring authentication. When the optional data parameter is supplied, the endpoint uses attacker-controlled flow data (containing arbitrary Python code in node definitions) instead of the stored flow data from the database. This code is passed to exec() with zero sandboxing, resulting in unauthenticated remote code execution. This is distinct from CVE-2025-3248, which fixed /api/v1/validate/code by adding authentication. The build_public_tmp endpoint is designed to be unauthenticated (for public flows) but incorrectly accepts attacker-supplied flow data containing arbitrary executable code. This issue has been fixed in version 1.9.0.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-33017. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are unknown but a public exploit is available.
The exploit is available at exploit-db.com. It is declared as attacked. The CISA Known Exploited Vulnerabilities Catalog lists this issue since 03/25/2026 with a due date of 04/08/2026:
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Exploit-DB (52627). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Eval injectionCWE: CWE-95 / CWE-94 / CWE-74
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Attacked
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
KEV Added: 🔒
KEV Due: 🔒
KEV Remediation: 🔒
KEV Ransomware: 🔒
KEV Notice: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔒
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
03/18/2026 Advisory disclosed03/18/2026 VulDB entry created
07/14/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2026-33017 (🔒)
GCVE (CVE): GCVE-0-2026-33017
GCVE (VulDB): GCVE-100-351515
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/18/2026 09:25Updated: 07/14/2026 02:28
Changes: 03/18/2026 09:25 (51), 03/23/2026 10:26 (14), 03/25/2026 19:44 (17), 03/26/2026 09:21 (12), 07/14/2026 02:28 (3)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.