What it is
CVE-2026-51886 is an unauthenticated vulnerability affecting Langflow-ai langflow. langflow-ai langflow v1.9.3 is affected by: Code Injection. The impact is: execute arbitrary code (remote).
Vulnerability Intelligence
langflow
Langflow-ai / langflow
Exploitation attempts observed by Previdian sensors. They do not show that the target was vulnerable or that the attempt succeeded.
26
Attempts observed
8
Unique attacker IPs
6
Attacker countries
DK · ID · NL · RU · SE · US
2
Sensors observed
CVE-2026-51886 exploitation attempts over the last 71 days
Daily events observed by Previdian sensors
Updated 22 Nov 2026
Decision summary
Direct answers before the deeper technical record.
What it is
CVE-2026-51886 is an unauthenticated vulnerability affecting Langflow-ai langflow. langflow-ai langflow v1.9.3 is affected by: Code Injection. The impact is: execute arbitrary code (remote).
Have exploitation attempts been observed?
Yes. Previdian sensors have observed 26 exploitation attempts, 8 unique attacker IPs, and 6 countries targeting CVE-2026-51886. First observed Aug 15, 2026; last observed Nov 09, 2026. Confidence is confirmed.
Who is affected?
Langflow-ai / langflow.
What should we do?
Patch immediately, validate internet-facing exposure, and monitor for matching requests.
Overview
langflow-ai langflow v1.9.3 is affected by: Code Injection. The impact is: execute arbitrary code (remote). The component is: src/backend/base/langflow/api/v1/validate.py:validate-post_validate_code-a-real-authenticated-http-post-to-api-v1. The attack vector is: Attack surface: HTTP or browser-backed service path.
A public-facing route accepts raw Python source and forwards it into a server-side compile/exec validation path without any visible entitlement guard. ¶¶ A weakness has been identified in langflow-ai langflow up to 1.9.3. langflow contains a code injection vulnerability in validate-post_validate_code-a-real-authenticated-http-post-to-api-v1 (src/backend/base/langflow/api/v1/validate.py:13). An authenticated attacker can execute arbitrary Python code on the server by submitting malicious code to the /api/v1/validate/code endpoint, which directly executes user-supplied code without sandboxing or security controls.
Exploitation evidence
Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.
Previdian
Previdian sensors observed exploitation attempts targeting this vulnerability.
Previdian sensor
Previdian sensors observed exploitation attempts targeting this vulnerability.
Per-source evidence links for KEV attestations are available through the Previdian API.
Request a Demo| Source | Added |
|---|---|
| Previdian Sensors First | 2026-10-06 10:31 UTC |
Operational indicators for this CVE are listed under Detection.
Sensor telemetry
Previdian sensor observations are exploitation attempts targeting this vulnerability. They do not show that the target was vulnerable or that the attempt succeeded. The cards and chart show volume, unique attackers, and daily activity.
First observed 15 Aug 2026 · Last observed 09 Nov 2026
Enterprise includes sensor region and window summaries, plus raw IPs, paths, User-Agents, and payloads.
Detection
Make the evidence actionable in scanner, SOC, and edge-control workflows.
Request targets, User-Agents, and callback host details are available on 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 on Enterprise.
Sensor-derived attacker IP indicators are available on Enterprise under Detection and through the API.
Request a DemoRisk and context
CVSS v3.1
Potential damage if exploited. Separate from whether attackers are using it.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.
Recent mention · Github Advisory Database (PIP)
###Summary: A critical Authenticated Remote Code Execution (RCE) vulnerability exists in the validate_code function of Langflow. The /api/v1/validate/code endpoint, meant to validate user-supplied code, leverages Python's exec() function. While it attempts to restrict...
Read full advisoryRecent mention · Github Advisory Database (PIP)
[langflow] Langflow: Title Authenticated Remote Code Execution in validate_code via Malicious Decorators DescriptionGithub Advisory Database (PIP) · 05 Oct 2026
###Summary: A critical Authenticated Remote Code Execution (RCE) vulnerability exists in the validate_code function of Langflow. The /api/v1/validate/code endpoint, meant to validate user-supplied code, leverages Python's exec() function. While it attempts to restrict execution to function definitions, it fails to account for decorators, which are evaluated at definition time. This allows any authenticated user to execute arbitrary code on the server, resulting in a full system compromise. Details The vulnerability is located in src/lfx/src/lfx/custom/validate.py(exposed via...
Recent mention · Github Advisory Database (PIP)
[langflow] Duplicate Advisory: Title Authenticated Remote Code Execution in validate_code via Malicious Decorators DescriptionGithub Advisory Database (PIP) · 02 Oct 2026
Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-w584-2h2r-2hvf. This link is maintained to preserve external references. Original Description langflow-ai langflow v1.9.3 is affected by: Code Injection. The impact is: execute arbitrary code (remote). The component is: src/backend/base/langflow/api/v1/validate.py:validate-post_validate_code-a-real-authenticated-http-post-to-api-v1. The attack vector is: Attack surface: HTTP or browser-backed service path. A public-facing route accepts raw Python source and forwards it into a server-side compile/exec...
API
Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.
GET /api/v2/enterprise/kevs/CVE-2026-51886
Sample API response{
"cve_id": "CVE-2026-51886",
"confidence": "Confirmed",
"cvss_score": 9.8,
"cvss_estimated": false,
"epss_score": 0.00602,
"exploit_status": {
"exploited_in_the_wild": true,
"active_exploitation_observed": true
},
"sensor_telemetry": { "attempts": 26, "sensors": 2 }
}
Timeline
00:20 UTC
Previdian customers had 10 hours of early warning before Previdian KEV.
00:00 UTC
Vulnerability disclosed publicly
03:56 UTC
Indicators of compromise recorded
02:06 UTC
Previdian sensors observed exploitation attempts targeting this vulnerability.
00:00 UTC
Identifier reserved by the CNA