LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27966: Langflow has Remote Code Execution in CSV Agent

Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to version 1.8.0, the CSV Agent node in Langflow hardcodes `allow_dangerous_code=True`, which automatically exposes LangChain’s Python REPL tool (`python_repl_ast`). As a result, an attacker can execute arbitrary Python and OS commands on the server via prompt injection, leading to full Remote Code Execution (RCE). Version 1.8.0 fixes the issue.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Langflow versions before 1.8.0 can let an unauthenticated attacker turn a CSV Agent prompt into server-side code execution. If Langflow is reachable by users or the internet, this can threaten the host’s data, integrity, and availability. The vendor advisory says version 1.8.0 fixes the issue.

Executive priority

Treat as urgent for any reachable Langflow deployment. Remote code execution can enable full server compromise. Prioritize upgrade and exposure review ahead of routine maintenance for affected systems.

Technical view

CVE-2026-27966 affects Langflow < 1.8.0. The CSV Agent node hardcoded LangChain’s dangerous code execution path, exposing the Python REPL tool. Prompt injection could execute arbitrary Python and OS commands on the Langflow server. The CVSS 3.1 score is 9.8, mapped to CWE-94.

Likely exposure

Highest concern is any Langflow deployment before 1.8.0 using or exposing the CSV Agent node, especially network-accessible instances. The source bundle does not identify specific deployment defaults, cloud services, or authentication configurations.

Exploitation context

The advisory describes unauthenticated, network-reachable remote code execution with low attack complexity and no user interaction. CISA KEV status is false in the provided data, and no cited source confirms active exploitation.

Researcher notes

Evidence is strong for affected version range, root cause, and fixed version based on the GitHub advisory and commit. The provided sources do not include proof-of-concept details, observed exploitation, or additional compensating controls beyond upgrading/checking vendor guidance.

Mitigation direction

  • Upgrade Langflow to version 1.8.0 or later.
  • Inventory Langflow instances and identify versions below 1.8.0.
  • Restrict access to Langflow until upgraded, especially from untrusted networks.
  • Review vendor advisory and commit for any environment-specific guidance.

Validation and detection

  • Confirm installed Langflow version is 1.8.0 or later.
  • Check whether CSV Agent workflows exist in deployed projects.
  • Verify Langflow is not exposed to untrusted networks unnecessarily.
  • Review recent Langflow server activity for suspicious execution or access patterns.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-27966 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-27966Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
langflow-ailangflow< 1.8.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.