CVE-2026-33309: langflow: Path Traversal enables file access

GHSA-g2j9-7rj2-gm6cCRITICALPoC AVAILABLECISA: ATTEND
Published March 24, 2026
CISO Take

CVE-2026-33309 is a critical RCE in Langflow (CVSS 9.9) that bypasses the previously-issued patch for CVE-2025-68478. Any authenticated user — including trial accounts — can write arbitrary files to the host via a crafted multipart upload, leading to full system compromise. Upgrade to Langflow 1.9.0 immediately; if patching is not possible today, restrict access to the file upload endpoint and audit all authenticated accounts.

What is the risk?

CRITICAL. CVSS 9.9 with network-reachable attack vector, low complexity, and only low privilege required — meaning any authenticated user is a potential attacker. The Changed scope indicator signals cross-boundary impact: a compromise of the Langflow process can pivot to the underlying host, adjacent containers, or connected AI infrastructure. The fact that this is a patch bypass (not a novel discovery) raises the threat level further: defenders who believed they were protected by the CVE-2025-68478 fix are still exposed. Langflow is widely deployed in enterprise AI pipelines, RAG systems, and agent orchestration environments, significantly broadening blast radius.

What systems are affected?

PackageEcosystemVulnerable RangePatched
Langflowpip>= 1.2.0, < 1.9.01.9.0
156.2KPushed 5d ago18% patched~75d to patchFull package profile →

Do you use Langflow? You're affected.

How severe is it?

CVSS 3.1
9.9 / 10
EPSS
13.5%
chance of exploitation in 30 days
Higher than 96% of all CVEs
Exploitation Status
Exploit Available
Exploitation: MEDIUM
Sophistication
Trivial
Exploitation Confidence
medium
✓VulnCheck KEV (exploitation reported — broader/earlier than CISA) — Oct 2026
○CISA SSVC: Public PoC
○Public PoC indexed (trickest/cve)
○EPSS exploit prediction: 13%
Composite signal derived from CISA KEV, VulnCheck KEV, CISA SSVC, EPSS, Metasploit, Exploit-DB, trickest/cve, Nuclei templates, and inthewild.io exploitation reports.

What is the attack surface?

AVACPRUISCIA
AVNetwork
ACLow
PRLow
UINone
SChanged
CHigh
IHigh
AHigh

What should I do?

6 steps
  1. PATCH

    Upgrade Langflow to version 1.9.0 immediately — this is the only complete fix.

  2. WORKAROUND (if patching is delayed): Block or rate-limit POST /api/v2/files/ at the WAF/reverse proxy layer; require additional authentication for file upload operations.

  3. AUDIT

    Review all user accounts with access to the Langflow instance; revoke unnecessary low-privilege accounts.

  4. DETECT

    Monitor for unexpected file creation events outside Langflow's designated storage directory (e.g., writes to /etc/, /home/, Python site-packages, or cron directories); alert on new processes spawned by the Langflow service user.

  5. ISOLATE

    Run Langflow in a minimal container with read-only filesystem mounts where possible; restrict the service account to least-privilege OS permissions.

  6. VERIFY

    Scan your Langflow deployment logs for POST /api/v2/files/ requests with filenames containing '../', '%2e', encoded slashes, or absolute paths.

What does CISA's SSVC say?

DecisionAttend
Exploitationpoc
AutomatableNo
Technical Impacttotal

Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.

How is it classified?

Which compliance frameworks are affected?

This CVE is relevant to:

EU AI Act
Art.15-Accuracy, Robustness and CybersecurityArt.9-Risk Management System
ISO 42001
A.6.1.2-Information Security in AI System Development and OperationA.9.1-AI System Risk Treatment
NIST AI RMF
GOVERN-1.7-Processes and procedures are in place for decommissioning AI systemsMANAGE-2.2-Mechanisms to sustain AI risk management are planned
OWASP LLM Top 10
LLM05-Supply Chain VulnerabilitiesLLM07-Insecure Plugin DesignLLM08-Excessive Agency

Frequently Asked Questions

What is CVE-2026-33309?

CVE-2026-33309 is a critical RCE in Langflow (CVSS 9.9) that bypasses the previously-issued patch for CVE-2025-68478. Any authenticated user — including trial accounts — can write arbitrary files to the host via a crafted multipart upload, leading to full system compromise. Upgrade to Langflow 1.9.0 immediately; if patching is not possible today, restrict access to the file upload endpoint and audit all authenticated accounts.

Is CVE-2026-33309 actively exploited?

Proof-of-concept exploit code is publicly available for CVE-2026-33309, increasing the risk of exploitation.

How to fix CVE-2026-33309?

1. PATCH: Upgrade Langflow to version 1.9.0 immediately — this is the only complete fix. 2. WORKAROUND (if patching is delayed): Block or rate-limit POST /api/v2/files/ at the WAF/reverse proxy layer; require additional authentication for file upload operations. 3. AUDIT: Review all user accounts with access to the Langflow instance; revoke unnecessary low-privilege accounts. 4. DETECT: Monitor for unexpected file creation events outside Langflow's designated storage directory (e.g., writes to /etc/, /home/, Python site-packages, or cron directories); alert on new processes spawned by the Langflow service user. 5. ISOLATE: Run Langflow in a minimal container with read-only filesystem mounts where possible; restrict the service account to least-privilege OS permissions. 6. VERIFY: Scan your Langflow deployment logs for POST /api/v2/files/ requests with filenames containing '../', '%2e', encoded slashes, or absolute paths.

What systems are affected by CVE-2026-33309?

This vulnerability affects the following AI/ML architecture patterns: agent frameworks, RAG pipelines, LLM orchestration platforms, AI workflow automation, model serving.

What is the CVSS score for CVE-2026-33309?

CVE-2026-33309 has a CVSS v3.1 base score of 9.9 (CRITICAL). The EPSS exploitation probability is 13.47%.

What is the AI security impact?

Affected AI Architectures

agent frameworksRAG pipelinesLLM orchestration platformsAI workflow automationmodel serving

MITRE ATLAS Techniques

AML.T0010.001AI Software
AML.T0012Valid Accounts
AML.T0049Exploit Public-Facing Application
AML.T0050Command and Scripting Interpreter
AML.T0072Reverse Shell
AML.T0081Modify AI Agent Configuration
AML.T0083Credentials from AI Agent Configuration
AML.T0105Escape to Host

Compliance Controls Affected

EU AI Act: Art.15, Art.9
ISO 42001: A.6.1.2, A.9.1
NIST AI RMF: GOVERN-1.7, MANAGE-2.2
OWASP LLM Top 10: LLM05, LLM07, LLM08

What are the technical details?

Original Advisory

Langflow is a tool for building and deploying AI-powered agents and workflows. Versions 1.2.0 through 1.8.1 have a bypass of the patch for CVE-2025-68478 (External Control of File Name), leading to the root architectural issue within `LocalStorageService` remaining unresolved. Because the underlying storage layer lacks boundary containment checks, the system relies entirely on the HTTP-layer `ValidatedFileName` dependency. This defense-in-depth failure leaves the `POST /api/v2/files/` endpoint vulnerable to Arbitrary File Write. The multipart upload filename bypasses the path-parameter guard, allowing authenticated attackers to write files anywhere on the host system, leading to Remote Code Execution (RCE). Version 1.9.0 contains an updated fix.

Exploitation Scenario

An attacker with a low-privilege Langflow account (e.g., a compromised trial user or an insider threat) crafts a multipart HTTP POST to /api/v2/files/ with a filename such as '../../usr/lib/python3/dist-packages/langflow/malicious.py' or a path targeting a cron directory. The HTTP-layer ValidatedFileName check is bypassed because the underlying LocalStorageService performs no boundary containment — the filename passes through the storage layer unchanged. The server writes attacker-controlled Python code to the target path. On next Langflow process restart or scheduled execution, the injected module is imported and the attacker's payload executes with Langflow's process privileges. From there, the attacker establishes a reverse shell, exfiltrates API keys and LLM credentials stored in Langflow's configuration, poisons agent tool definitions to affect downstream AI pipeline consumers, and potentially pivots to connected databases or cloud infrastructure.

Weaknesses (CWE)

CWE-22 — Improper Limitation of a Pathname to a Restricted Directory: The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

  • [Implementation] Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylis
  • [Architecture and Design] For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.

Source: MITRE CWE corpus.

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Timeline

Published
March 24, 2026
Last Modified
June 6, 2026
First Seen
March 24, 2026

Related Vulnerabilities