CVE-2026-110186
Langflow OSS is affected by multiple vulnerabilities
No known exploitation. EPSS puts it in the 50th percentile. Fixed in 1.13.0.
No public exploit knownFix1.13.0Upgrade to this build
No ready-made check. Neither Nuclei nor OpenVAS has one for this CVE yet.
What to do
Find your product and version, then upgrade to the build on the right.
- IBM Langflow OSSAffected: ≥ 1.0.0, ≤ 1.12.8Upgrade to: after 1.12.8Stated by: CVE record
- LangflowAffected: ≥ 1.0.0, < 1.13.0Upgrade to: 1.13.0Stated by: NVD
Versions as the sources state them. Full version matrix after sign-in
Steps
Written by AI from the record- Check your Langflow OSS version — anything from 1.0.0 through 1.12.8 is affected.
- If deployed via pip, run: pip install langflow --upgrade.
- If deployed via Docker, pull and redeploy the updated image.
- Confirm the running instance reports version 1.13.0 or later.
- Until updated, restrict access to the Langflow interface so it is not reachable from the open internet.
pip install langflow --upgradeWhat it is
From the CVE record
IBM Langflow OSS 1.0.0 through 1.12.8 could allow a remote attacker to execute arbitrary code due to improper control of code generation.
In plain language
Written by AI from the recordLangflow OSS, a tool for building AI workflows, has a serious flaw that could let an attacker run their own code on your server, but it isn't currently being exploited and no attack tool exists yet — plan to update soon rather than drop everything.
Unauthenticated remote code execution in Langflow OSS versions 1.0.0 through 1.12.8 via improper control of code generation (CWE-94), fixed in 1.13.0.
If you're affected
- Full server takeover
- Exposure of connected AI/data pipelines
- Operational disruption
- Lateral movement into internal network
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.6% chance of exploitation activity in the next 30 days, which ranks it in the 50th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
12 events over 1 day, from the signal feeds we watch.
- Patch availablepatch available, patch available, record updated, record updated, record updated
- Patch availablepatch available, published, weakness classified, att&ck mapped, record updated
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Scored 9.8 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Langflow, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI