Vulnerability report

Active exploitation observed Confirmed confidence Not in CISA KEV

CVE-2026-105740

langflow Authenticated RCE Remote Code Execution

Langflow-ai / langflow · affected before 1.9.0

Severity
CVSS 9.9 · Critical
Confidence
Confirmed
Exploit status
Observed in sensors
EPSS
0.6%
First observed
19 Sep 2026
Last observed
13 Oct 2026

Decision summary

What security teams need to know first

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

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.

langflow-ai Affected
langflow
Before 1.9.0
Published
05 Oct 2026
Exploited Since
19 Sep 2026
Attack vector
Remote
Complexity
Low
Privileges
Low
User interaction
None

CVE References

Exploitation evidence

Why Previdian marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

Previdian

Recorded 11 Oct 2026

Previdian independently recorded this as exploited after first seeing it in honeypot sensors.

Active exploitation observed

Previdian sensor

First observed 19 Sep 2026

Previdian first observed exploitation attempts targeting this vulnerability in our honeypot sensors.

Known exploited vulnerability sources

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

First-party evidence of exploitation activity

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

0
1
0
0
0
0
0
0
0
10
12
3
0
12
0
4
0
0
0
0
13
17
43
333
327
247
18 Sep 24 Sep 30 Sep 6 Oct 13 Oct

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.

Start 14-day Pro trial

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
1,004
23
1

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Scanner coverage

No scanner integrations recorded yet.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

Attacker IP Indicators

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 access

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

9.9 Critical

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

From disclosure to observed exploitation

  1. 20:46 UTC

    CVE published

    Vulnerability disclosed publicly

  2. 19:11 UTC

    CVE ID reserved

    Identifier reserved by the CNA

  3. 03:14 UTC

    Indicators of compromise added (24)

    Indicators of compromise recorded

  4. 03:14 UTC

    Observed by Previdian sensors

    Evidence-backed exploitation signal

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

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 }
}