CVE-2026-51886: langflow · Code Injection
Affects langflowSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHublangflow-ai/langflowpkg:github/langflow-ai/langflowOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a patch or official fix is available, restrict access to the /api/v1/validate/code endpoint to trusted users only and consider disabling this functionality if possible. Monitor for suspicious activity from authenticated users. Avoid exposing this API endpoint publicly.
Description
Langflow-ai langflow version 1.9.3 and earlier contains a critical code injection vulnerability. An authenticated attacker can submit arbitrary Python code to the /api/v1/validate/code endpoint, which is executed on the server without sandboxing or security controls. This allows remote code execution with full impact on confidentiality, integrity, and availability.