What it is
CVE-2026-105740 is a vulnerability affecting Langflow-ai langflow. Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to 1.9.0, any authenticated Langflow user can achieve Remote Code...
Vulnerability report
langflow Authenticated RCE Remote Code Execution
Langflow-ai / langflow · affected before 1.9.0
Decision summary
Direct answers before the deeper technical record.
What it is
CVE-2026-105740 is a vulnerability affecting Langflow-ai langflow. Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to 1.9.0, any authenticated Langflow user can achieve Remote Code...
Is it exploited?
Yes. Previdian sensors observed exploitation attempts with confirmed confidence.
Who is affected?
Langflow-ai / langflow affected before 1.9.0.
What should we do?
Patch immediately, validate internet-facing exposure, and monitor for matching requests.
Overview
Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to 1.9.0, any authenticated Langflow user can achieve Remote Code Execution (RCE) on the server by adding an MCP server with the "Stdio" transport. The user-supplied command field is passed directly to bash -c "exec {command}" with zero validation, no allowlisting, and no sandboxing.
The command executes immediately when the server list is fetched. Additionally, the env field allows arbitrary environment variable injection (e.g., LD_PRELOAD, PATH override). This vulnerability is fixed in 1.9.0.
Exploitation evidence
Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.
Previdian
Previdian independently recorded this as exploited after first seeing it in honeypot sensors.
Previdian sensor
Previdian first observed exploitation attempts targeting this vulnerability in our honeypot sensors.
Per-source evidence links for KEV attestations are available through the Previdian Pro API.
Learn about Pro API access| Source | Added |
|---|---|
| Previdian Sensors First | 2026-10-11 17:42 UTC |
Operational indicators for this CVE are listed under Detection.
Sensor telemetry
Previdian sensors recorded exploitation attempts targeting this vulnerability. The cards and chart show volume, unique attackers, and daily activity.
1,022
Attempts observed
24
Unique attacker IPs
12
Attacker countries
BE · CN · DE · JP · KR · NG · PH · RU · SC · SG · TZ · US
1
Sensors observed
CVE-2026-105740 exploitation attempts over the last 26 days
Daily events observed by Previdian sensors
Updated 13 Oct 2026
First observed 19 Sep 2026 · Last observed 13 Oct 2026
Pro adds sensor region and window summaries. Enterprise adds raw IPs, paths, User-Agents, and payloads.
Detection
Make the evidence actionable in scanner, SOC, and edge-control workflows.
Request targets and User-Agents available in Pro. Callback host details available in Enterprise.
No scanner integrations recorded yet.
No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.
Learn about virtual patches →Attacker IP indicators observed · available in Pro and Enterprise.
Sensor-derived attacker IP indicators are available to Pro and Enterprise accounts under Detection and through the Pro API.
Learn about Pro API accessRisk and context
CVSS v3.1
Potential damage if exploited. Separate from whether attackers are using it.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.6%
Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.
Timeline
20:46 UTC
Vulnerability disclosed publicly
19:11 UTC
Identifier reserved by the CNA
03:14 UTC
Indicators of compromise recorded
03:14 UTC
Evidence-backed exploitation signal
Pro API
Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.
GET /api/v2/pro/kevs/CVE-2026-105740
Free JSON includes basic KEV fields{
"cve_id": "CVE-2026-105740",
"confidence": "Confirmed",
"cvss_score": 9.9,
"cvss_estimated": false,
"epss_score": 0.00589,
"exploit_status": {
"exploited_in_the_wild": true,
"active_exploitation_observed": true
},
"sensor_telemetry": { "attempts": 1022, "sensors": 1 }
}