CVE-2026-51888: Langflow: absolute path traversal allows arbitrary file write

HIGHPoC AVAILABLECISA: TRACK*
Published October 1, 2026
CISO Take

Langflow 1.8.4 and earlier contain an absolute path traversal flaw in the knowledge base creation endpoint (knowledge_bases.py), which lets an unauthenticated remote attacker write or overwrite files anywhere the Langflow process has permissions. It is rated High (CVSS 7.5, network, low complexity, no privileges, no user interaction), but the integrity-only impact is limited on paper: arbitrary file overwrite in a service that often runs with broad filesystem access can realistically be chained into code execution. Exploitation likelihood is currently low-to-moderate (EPSS 0.56%, around the 55th percentile), the CVE is not in CISA KEV, and there is no public exploit or Nuclei template. The only reference is a researcher gist, so details are public enough to be weaponized quickly. Langflow has a history of being targeted, so treat it as a patch-soon item. Upgrade past 1.8.4 as soon as a fixed release is available (confirm with the vendor advisory, since no fix version is listed in the data), and until then do not expose Langflow directly to the internet or untrusted networks. Also restrict access to the knowledge base endpoint at the reverse proxy.

Sources:NVDEPSSATLAS

What is the risk?

Medium-High. Exploitability is excellent (network, low complexity, no auth, no interaction), but impact is limited to integrity (I:H, C:N, A:N) and there is no evidence of exploitation in the wild (not in KEV, EPSS 0.56%, no public exploit or Nuclei template). The practical risk rises sharply for internet-exposed Langflow instances running as root or in containers with writable application, cron or SSH paths, where file overwrite can become remote code execution. No CWE or affected-version metadata is formally listed, so confidence in the exact scope is medium.

How does the attack unfold?

Initial Access
Attacker finds an exposed Langflow instance and reaches the knowledge base creation endpoint without authentication.
AML.T0049
Exploitation
Attacker submits a request with an absolute path, and the server writes or overwrites a file outside the intended storage directory.
AML.T0049
Persistence / Execution
Overwritten startup, config or code files cause attacker content to run on the next restart or scheduled task.
Impact
Integrity of the AI workflow host is compromised, exposing flows, RAG data and provider credentials.
AML.T0112

What systems are affected?

PackageEcosystemVulnerable RangePatched
Langflowpip—No patch
156.7KPushed 3d ago18% patched~76d to patchFull package profile →

Do you use Langflow? You're affected.

How severe is it?

CVSS 3.1
7.5 / 10
EPSS
0.6%
chance of exploitation in 30 days
Higher than 51% of all CVEs
Exploitation Status
Exploit Available
Exploitation: MEDIUM
Sophistication
Trivial
Exploitation Confidence
medium
○CISA SSVC: Public PoC
○Public PoC indexed (trickest/cve)
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
PRNone
UINone
SUnchanged
CNone
IHigh
ANone

What should I do?

1 step
  1. 1) Upgrade Langflow to the first release after 1.8.4 that fixes this issue (verify in the vendor GitHub advisory/releases). 2) Until patched, remove public exposure: place Langflow behind a VPN, authenticated reverse proxy or IP allowlist, and block or restrict POST requests to the knowledge base creation endpoint (/api/v1/knowledge_bases). 3) Run the service as a non-root user in a container with a read-only root filesystem and writable mounts limited to the data directory. 4) Detection: alert on requests to the knowledge base creation endpoint containing absolute paths (leading '/' or drive letters) or '..' sequences, on unexpected file modifications outside the Langflow data directory (file integrity monitoring on app code, cron, SSH authorized_keys), and on new files owned by the Langflow user. 5) Audit instances for unexpected changes and rotate secrets if tampering is suspected.

What does CISA's SSVC say?

DecisionTrack*
Exploitationpoc
AutomatableYes
Technical Impactpartial

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 cybersecurity
ISO 42001
A.6.2.6-AI system operation and monitoring
NIST AI RMF
MANAGE 2.3-Respond to and recover from previously unknown risks
OWASP LLM Top 10
LLM03-Supply Chain

Frequently Asked Questions

What is CVE-2026-51888?

Langflow 1.8.4 and earlier contain an absolute path traversal flaw in the knowledge base creation endpoint (knowledge_bases.py), which lets an unauthenticated remote attacker write or overwrite files anywhere the Langflow process has permissions. It is rated High (CVSS 7.5, network, low complexity, no privileges, no user interaction), but the integrity-only impact is limited on paper: arbitrary file overwrite in a service that often runs with broad filesystem access can realistically be chained into code execution. Exploitation likelihood is currently low-to-moderate (EPSS 0.56%, around the 55th percentile), the CVE is not in CISA KEV, and there is no public exploit or Nuclei template. The only reference is a researcher gist, so details are public enough to be weaponized quickly. Langflow has a history of being targeted, so treat it as a patch-soon item. Upgrade past 1.8.4 as soon as a fixed release is available (confirm with the vendor advisory, since no fix version is listed in the data), and until then do not expose Langflow directly to the internet or untrusted networks. Also restrict access to the knowledge base endpoint at the reverse proxy.

Is CVE-2026-51888 actively exploited?

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

How to fix CVE-2026-51888?

1) Upgrade Langflow to the first release after 1.8.4 that fixes this issue (verify in the vendor GitHub advisory/releases). 2) Until patched, remove public exposure: place Langflow behind a VPN, authenticated reverse proxy or IP allowlist, and block or restrict POST requests to the knowledge base creation endpoint (/api/v1/knowledge_bases). 3) Run the service as a non-root user in a container with a read-only root filesystem and writable mounts limited to the data directory. 4) Detection: alert on requests to the knowledge base creation endpoint containing absolute paths (leading '/' or drive letters) or '..' sequences, on unexpected file modifications outside the Langflow data directory (file integrity monitoring on app code, cron, SSH authorized_keys), and on new files owned by the Langflow user. 5) Audit instances for unexpected changes and rotate secrets if tampering is suspected.

What systems are affected by CVE-2026-51888?

This vulnerability affects the following AI/ML architecture patterns: LLM orchestration frameworks, RAG pipelines, agent frameworks, knowledge base / vector ingestion pipelines, low-code AI workflow platforms.

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

CVE-2026-51888 has a CVSS v3.1 base score of 7.5 (HIGH). The EPSS exploitation probability is 0.64%.

What is the AI security impact?

Affected AI Architectures

LLM orchestration frameworksRAG pipelinesagent frameworksknowledge base / vector ingestion pipelineslow-code AI workflow platforms

MITRE ATLAS Techniques

AML.T0010.001AI Software
AML.T0049Exploit Public-Facing Application
AML.T0112Machine Compromise

Compliance Controls Affected

EU AI Act: Art. 15
ISO 42001: A.6.2.6
NIST AI RMF: MANAGE 2.3
OWASP LLM Top 10: LLM03

What are the technical details?

Original Advisory

langflow-ai langflow v1.8.4 is affected by: Directory Traversal. The impact is: Arbitrary file write outside the intended workspace or storage boundary.. The component is: src/backend/base/langflow/api/v1/knowledge_bases.py:knowledge_bases-create_knowledge_base-a-live-http-post-to-create-knowledge-base. The attack vector is: Attack surface: HTTP or browser-backed service path. A public-facing upload or HTTP route handler forwards an attacker-controlled path or filename into host file creation without any visible boundary enforcement. ¶¶ A weakness has been identified in langflow-ai langflow up to 1.8.4. langflow contains an absolute path traversal vulnerability in knowledge_bases-create_knowledge_base-a-live-http-post-to-create-knowledge-base (src/backend/base/langflow/api/v1/knowledge_bases.py:51). An attacker can write or overwrite files outside the intended working directory by providing absolute paths in the knowledge base creation endpoint.

Exploitation Scenario

An attacker scans for internet-exposed Langflow instances and sends an unauthenticated POST to the knowledge base creation endpoint, supplying an absolute path such as a Python module in the site-packages directory, a cron file or an SSH authorized_keys file as the knowledge base name or location. The server writes attacker-influenced content to that path. The attacker overwrites a file that is executed on the next restart or schedule, gaining code execution in the AI workflow host. From there they read API keys for LLM providers and vector databases from the environment, and manipulate flows and RAG data.

CVSS Vector

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

Timeline

Published
October 1, 2026
Last Modified
October 6, 2026
First Seen
October 1, 2026

Related Vulnerabilities