Skip to main content
← All vulnerabilities
CVE-2026-110196EUVD-2026-113130GHSA-V6HG-Q5XW-V79W

Langflow OSS is affected by multiple vulnerabilities

Affects Langflow OSS 1.0.0 through 1.12.4. Fixed in 1.12.5.

Published
Last modified
published
Not listed in CISA KEV
Specific setups only
Fix
Fixed in 1.12.5
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

IBM Langflow OSS is affected, allowing a remote attacker with a low-privileged authenticated account to bypass administrator-only restrictions. This could let the attacker execute arbitrary code on the affected server.

Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.

Read the original description

IBM Langflow OSS 1.0.0 through 1.12.4 could allow a remote attacker with a low-privileged authenticated account to bypass the administrator-only restriction and execute arbitrary code on the server by configuring a built-in code-execution component with attacker-supplied inputs.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • IBM Langflow OSS

    From 1.0.0 · through 1.12.4

References 1

ibm.com

FAQ

Questions about CVE-2026-110196

What does this mean?

An attacker can bypass the administrator-only restriction and run arbitrary code on the server by configuring a built-in code-execution component with attacker-supplied inputs.Source: ibm.com

Am I affected, and how do I check?

Langflow OSS versions 1.0.0 through 1.12.4 are affected. Check the installed Langflow OSS version to see whether it falls in that range.Source: ibm.com

What should I do about it?

Upgrade Langflow OSS to version 1.12.5, which IBM strongly recommends addressing now. No workaround is listed in the facts.Source: ibm.com

Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data