IBM Langflow OSS 1.0.0 through 1.12.4 could allow a remote attacker to trigger pre-existing stored Python component
Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium.
Data as of 29 Oct 2026, 19:32 UTC
Thin evidence
One scorer or none| CNA (ibm) | CVSS 3.1 | 6.5 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBMLangflow OSS | Affected
| Fixed in– |
AI-suggested
Until a fix is available, restrict access to public workflows and monitor usage to mitigate risk.
Description
IBM Langflow OSS versions 1.0.0 through 1.12.4 contain a vulnerability that allows a remote attacker to execute stored Python component code within a public workflow. This execution occurs under the flow owner's runtime context on the server, bypassing intended trust boundaries that restrict public execution to server-trusted code. The vulnerability is identified as CVE-2026-18894 and has a medium severity rating with a CVSS score of 6.5.