Vulnerability report

Active exploitation observed Confirmed confidence Not in CISA KEV

CVE-2026-0769

Langflow Remote Code Execution

Langflow · 1.3.2

Severity
CVSS 9.8 · Critical
Confidence
Confirmed
Exploit status
Observed in sensors
EPSS
41.7%
First observed
27 Aug 2026
Last observed
10 Oct 2026

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2026-0769 is an unauthenticated vulnerability affecting Langflow. Langflow eval_custom_component_code Eval Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute...

Is it exploited?

Yes. Previdian sensors observed exploitation attempts with confirmed confidence.

Who is affected?

Langflow 1.3.2.

What should we do?

Patch immediately, validate internet-facing exposure, and monitor for matching requests.

Overview

Langflow eval_custom_component_code Eval Injection Remote Code Execution Vulnerability

Langflow eval_custom_component_code Eval Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Langflow. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the implementation of eval_custom_component_code function. The issue results from the lack of proper validation of a user-supplied string before using it to execute python code. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-26972.

Langflow Affected
Langflow
1.3.2
Published
23 Jan 2026
Exploitation Reported
27 Aug 2026
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

Tags

python

CVE References

  • CVE Record CVE.org · CVE Record https://www.cve.org/CVERecord?id=CVE-2026-0769
  • ZDI-26-035 zerodayinitiative.com · CVE Record https://www.zerodayinitiative.com/advisories/ZDI-26-035/

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 27 Aug 2026

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

Active exploitation observed

Previdian sensor

First observed 27 Aug 2026

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

Proof of concept available

GitHub

Recorded 02 Sep 2026

Public scanner or PoC coverage increases practical exploitability.

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-09-18 07:40 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.

762

Attempts observed

55

Unique attacker IPs

25

Attacker countries

AZ · BR · DE · DK · FR · HK · ID · IN · JP · KH · KR · LT · MX · NL · PK · RS · RU · SA · SG · TH · TR · TW · US · VN · XK

1

Sensors observed

CVE-2026-0769 exploitation attempts over the last 47 days

Daily events observed by Previdian sensors

Updated 11 Oct 2026

0
1
0
0
0
1
0
0
2
0
0
0
0
0
0
0
378
30
61
56
22
11
15
24
0
22
0
0
2
0
0
28
5
0
0
4
5
2
12
0
2
1
45
9
12
12
0
26 Aug 5 Sep 15 Sep 25 Sep 11 Oct

First observed 27 Aug 2026 · Last observed 10 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
2
16
3

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.0

9.8 Critical

Potential damage if exploited. Separate from whether attackers are using it.

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

EPSS

41.7%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Potential Proof of Concepts

These PoCs are unverified and could contain malware. Use at your own risk.

rmhowe425/POC-CVE-2026-0769

github · Created 2026-09-02 23:34:00 UTC · 0 stars · AI assessment 90%

Timeline

From disclosure to observed exploitation

  1. 23:34 UTC

    Public PoC available

    Public proof-of-concept code published

  2. 23:58 UTC

    Indicators of compromise added (55)

    Indicators of compromise recorded

  3. 23:58 UTC

    Observed by Previdian sensors

    Evidence-backed exploitation signal

  4. 03:28 UTC

    CVE published

    Vulnerability disclosed publicly

  5. 22:50 UTC

    CVE ID reserved

    Identifier reserved by the CNA

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

Free JSON includes basic KEV fields
{
  "cve_id": "CVE-2026-0769",
  "confidence": "Confirmed",
  "cvss_score": 9.8,
  "cvss_estimated": false,
  "epss_score": 0.41695,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": true
  },
  "sensor_telemetry": { "attempts": 762, "sensors": 1 }
}